All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre McCurdy <armccurdy@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Releases of BitBake to package for Fedora?
Date: Mon, 6 Nov 2017 11:16:06 -0800	[thread overview]
Message-ID: <CAJ86T=VN8PDUWrNAuW=y_RpUEoOtGa-TyufyGwbZT6APPMsm9A@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0La7eK950Up4033qmX_1PQnS5nJJt4zb_P7uJn1Y8eO0QQ@mail.gmail.com>

On Mon, Nov 6, 2017 at 3:33 AM, Burton, Ross <ross.burton@intel.com> wrote:
> The bitbake API isn't really stable and has a reasonable amount of change,
> so if you were to package it then there's a good chance it would be out of
> date within six months and people who wanted to use the latest oe-core
> release against the packaged bitbake would hit API version errors.  The
> recommended usage is to bundle in some way bitbake and the metadata
> (combo-layer, submodules, repo, whatever).
>
> As such there are no tarballs.  There are branches for each version and
> commits where the version is bumped, if you're really determined to package
> a snapshot.

If there's no realistic hope of (or need for) using bitbake standalone
then maybe it's time to move bitbake into oe-core?


  reply	other threads:[~2017-11-06 19:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05 15:09 Releases of BitBake to package for Fedora? Neal Gompa
2017-11-06 11:22 ` Alexander Kanavin
2017-11-06 11:33 ` Burton, Ross
2017-11-06 19:16   ` Andre McCurdy [this message]
2017-11-06 19:18     ` Paul Eggleton
2017-11-06 23:27       ` Andre McCurdy
2017-11-07  1:08         ` Paul Eggleton
2017-11-08 11:58 Neal Gompa
2017-11-09  3:48 ` Paul Eggleton
2017-11-09  3:53   ` Neal Gompa
2017-11-09  9:22     ` Martin Jansa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ86T=VN8PDUWrNAuW=y_RpUEoOtGa-TyufyGwbZT6APPMsm9A@mail.gmail.com' \
    --to=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.