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.

Ross

On 5 November 2017 at 15:09, Neal Gompa <ngompa13@gmail.com> wrote:

> Hey all,
>
> Apologies if this is the wrong mailing list for this, but I'm looking
> reintroduce BitBake into Fedora, but it seems like there hasn't been
> releases in two years. I also cannot identify anywhere that provides
> tarballs of BitBake to package.
>
> Am I not looking in the right place?
>
> I looked in the following locations:
>
> * GitHub: https://github.com/openembedded/bitbake
> * OE Git: http://git.openembedded.org/bitbake/
> * Yocto downloads page: https://www.yoctoproject.org/downloads/tools
>
> The Fedora package previously referenced snapshot tarballs generated
> by tagged releases in OE Git, but there haven't been new tagged
> releases in two years.
>
> I'd appreciate any help here.
>
> Thanks in advance and best regards!
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>