Re: Release team now using gnome-build-meta repository, not JHBuild

[mcatanzaro]

On Sun, Jan 21, 2018 at 6:02 AM, Tristan Van Berkom 
 wrote:

gexiv2 is listed as a system dependency, which strikes me as a bit odd
seeing as it's a requirement for some GNOME modules and it's hosted in
GNOME - I'm new to the release team and will have to figure out the
reasoning behind this.


We used to prefer to move modules from core-deps into sysdeps when 
possible, to reduce the number of modules that can cause build failures 
in JHBuild. That's not really going to be an issue anymore. I think 
moving gexiv2 to core-deps would be uncontroversial, if there's desire 
to do so, especially since it's hosted on GNOME infrastructure.



For now, the actual sysdeps we use to populate a base runtime to build
against are controlled by this list[2], and is basically generated 
from

packages in debian testing - until the freedesktop-sdk project evolves
and we start generating bootable VMs with a combination of that, and
GNOME build metadata, I should move that repo over to GNOME's gitlab
and re-enable the automation of generating the images it creates (I've
been doing this manually in order to avoid unnecessary rebuilds).


Tristan mentions that gexiv2 is a system dependency... that means it 
was never built in JHBuild before now, so it's not going to be built in 
BuildStream either (unless we add it to the core-deps project).


Under JHBuild, our rule was that GNOME modules can depend on a system 
dependency only if it's present in the latest stable releases of both 
Fedora and Ubuntu. Now, under BuildStream, it's much easier to add a 
new version of a system dependency. Once the new gexiv2 package enters 
Debian testing, you can simply create a merge request to add it to 
multistrap.conf.in, the file Tristan pointed to in his last mail, and 
then GNOME modules can begin to depend on it.


Alternatively, you could create a merge request or issue report to add 
it to the core-deps project.


Michael

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Release team now using gnome-build-meta repository, not JHBuild

[mcatanzaro]

Hi,

On Sun, Jan 21, 2018 at 3:16 AM, Jens Georg  wrote:
So, following up on that and also on the libgepub thread: Which 
places do I have to modify if I were to switch the ABI and API 
version of gexiv2 (to either keep depending entities on the old 
stable branch or to the new branch or provide both etc) ? Only 
gnome-build-meta as mandatory, jhbuild as goodwill? What about 
continous?


Please do continue to update Continuous as needed for the time being. 
The future plan is to generate the Continuous manifest from 
gnome-build-meta, so that we don't have all this metadata specified in 
three different places, but replacing the manifest in gnome-sdk-images 
is more important to do first. (gnome-sdk-images is more 
lightly-maintained, and yet it's our only set of build definitions that 
directly affects our users.) Unfortunately, that's not likely to be 
ready for 3.28, so we'll need to be patient in the meantime. Hopefully 
later this year, we'll be able to announce that the Continuous manifest 
is gone. Again, thank Tristan and Codethink for this. ;)


I personally wouldn't touch JHBuild anymore unless you want to continue 
using JHBuild yourself and benefit from the changes you make, but it's 
up to you. JHBuild's developer workflow is still IMO better than what 
is currently provided by BuildStream, and we're used to using it for 
many years, so it's understandable if some community members desire to 
keep it working. (But release team considers it too fragile, and we 
really want to reduce the number of build definitions that we have to 
maintain.)


Michael

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Release team now using gnome-build-meta repository, not JHBuild

[Tristan Van Berkom]

Hi Jens,

Hurried reply whilst getting ready to go to airport...

On Sun, 2018-01-21 at 10:16 +0100, Jens Georg wrote:
> > On Sat, 2018-01-20 at 11:06 -0600, mcatanz...@gnome.org wrote:
> 
> > Hi all,
> > 
> > This bears repeating: the release team will no longer maintain
> > JHBuild 
> > or the JHBuild modulesets. When adding or removing a dependency from 
> > your module, please now update gnome-build-meta instead.
> 
> So, following up on that and also on the libgepub thread: Which places
> do I have to modify if I were to switch the ABI and API version of
> gexiv2

gexiv2 is listed as a system dependency, which strikes me as a bit odd
seeing as it's a requirement for some GNOME modules and it's hosted in
GNOME - I'm new to the release team and will have to figure out the
reasoning behind this.

Also, your question makes me realize I need to clarify some more things
about sysdeps and how they have changed, there is a longer term plan
which involves collaboration with the newly created freedesktop-sdk
project (see: gitlab project[0] and mailing list[1]) for building a
well integrated system which I will try to blog about soon.

For now, the actual sysdeps we use to populate a base runtime to build
against are controlled by this list[2], and is basically generated from
packages in debian testing - until the freedesktop-sdk project evolves
and we start generating bootable VMs with a combination of that, and
GNOME build metadata, I should move that repo over to GNOME's gitlab
and re-enable the automation of generating the images it creates (I've
been doing this manually in order to avoid unnecessary rebuilds).

Cheers,
-Tristan


[0]: https://gitlab.com/freedesktop-sdk
[1]: https://lists.freedesktop.org/mailman/listinfo/freedesktop-sdk
[2]: 
https://gitlab.com/BuildStream/debootstrap-ostree/blob/master/data/multistrap.conf.in

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Release team now using gnome-build-meta repository, not JHBuild

[Jens Georg]

On Sat, 2018-01-20 at 11:06 -0600, mcatanz...@gnome.org wrote:

> Hi all,
> 
> This bears repeating: the release team will no longer maintain
> JHBuild 
> or the JHBuild modulesets. When adding or removing a dependency from 
> your module, please now update gnome-build-meta instead.

So, following up on that and also on the libgepub thread: Which places
do I have to modify if I were to switch the ABI and API version of
gexiv2 (to either keep depending entities on the old stable branch or
to the new branch or provide both etc) ? Only gnome-build-meta as
mandatory, jhbuild as goodwill? What about continous?
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list