Re: GNOME Modulesets in BuildStream - Baby Steps

[Javier Jardón <jjardon gnome org>]

On 31 October 2017 at 10:36, Tristan Van Berkom
<tristan vanberkom codethink co uk> wrote:
<snip>

> I'm hoping that we can take a different strategy with a converted
> BuildStream project than we had with JHBuild, i.e. using git.
>
> I would suggest that we keep a 'gnome-modulesets' git repository where
> we always build master of everything, on the master branch, and that we
> branch for every stable release.
>
> We can also tag stable releases in such a way that we know that builds
> from the gnome-modulesets repo at a given tag, produce exactly the same
> results when one attempts to build it elsewhere (could potentially do
> this for dev releases too if that's interesting).
>
> Probably this is going to need a bit more thought, but I think it's
> approximately correct and will be cleaner than supporting every version
> of GNOME in the same master branch.

That was exactly the reason why [1] was created; split jhbuild from
the modulesets itself and use git to track ther gnome versions as you
describe
Unfortunatelly it never happened because [2] was never finish
Maybe makes sense to use that repo to push the converted bst recipes?

Cheers,
Javier

PS: Thanks for the quick BuildStream fix btw!

[1] https://git.gnome.org//browse/gnome-modulesets
[2] https://bugzilla.gnome.org/show_bug.cgi?id=675873