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

Hi Tristan, > > > 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

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

Sorry I've been slow on this thread, it's an inopportune time as I'm stuck in all day meetings all week... On Wed, 2018-01-24 at 14:24 -0600, mcatanz...@gnome.org wrote: > > On Wed, Jan 24, 2018 at 2:11 PM, Florian Müllner   > wrote: > > Really, the only thing I disagree with

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

On Wed, Jan 24, 2018 at 2:11 PM, Florian Müllner wrote: Really, the only thing I disagree with is that RT appears to actively discourage maintainers from updating JHbuild before everyone actually has the option to make the switch - sure, if updating GTK+ fails for me

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

Oh my. I certainly did not intend to start a rant thread, sorry for that. To clarify: I am not complaining that RT is taking away my favorite toy. JHbuild is a great tool when it works, but it still breaks far too often for newcomers or non-regulars. And as you rightly point out, this is not

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

On Wed, Jan 24, 2018 at 02:28:26AM +0200, Alberts Muktupāvels wrote: > Sorry if that already is posted somewhere, but is there at least some kind > of migration guide/tutorial? See the first e-mail of this thread. -- Sébastien ___ desktop-devel-list

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

On Wed, Jan 24, 2018 at 12:22 AM, Marco Trevisan (Treviño) wrote: > Il 22/01/2018 14:34, mcatanz...@gnome.org ha scritto: > > On Mon, Jan 22, 2018 at 7:25 AM, mcatanz...@gnome.org wrote: > >> Were you actually using JHBuild to run integrated system components > >> (gnome-shell,

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

Il 22/01/2018 14:34, mcatanz...@gnome.org ha scritto: > On Mon, Jan 22, 2018 at 7:25 AM, mcatanz...@gnome.org wrote: >> Were you actually using JHBuild to run integrated system components >> (gnome-shell, gnome-session)? If so, how? I was not aware that that >> was even possible nowadays. >> >>

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

On Mon, Jan 22, 2018 at 3:12 PM, Bastien Nocera wrote: Or c) nobody's needed to recompile at-spi-core2 because it hasn't changed in significant ways in years and the distro provided versions work just fine. My at-spi-core checkout dates back from 2013. I, and I suspect a

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

Hi all, This will be a long email, so TL;DR: o At this time you can keep using JHBuild for these few cases where testing is very difficult, you can even do so indefinitely. o For these few modules who dont benefit directly at development time from the release team's official

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

On Mon, 2018-01-22 at 14:31 -0600, mcatanz...@gnome.org wrote: > > > I'll use one specific anecdote. On October 30, the Autotools build > files were removed from at-spi2-core. The accompanying JHBuild > moduleset update switching it to use meson was pushed by Philip > Withnall (thanks!) on

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

>But I'm only speaking for the release team here, not the entire community - I know that answer doesn't actually solve the problem, but hopefully that explains our thinking. Definitely, I imagined this is just a side effect of the release team not using JHbuild anymore, which I understand. Just

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

On Mon, Jan 22, 2018 at 12:56 PM, Carlos Soriano wrote: What's the workflow for those before a proper solution is done? Or are the developers of those modules expected to maintain JHbuild on the meantime? Thanks Carlos; this is an important question. Let me provide a

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

Adding on top of Florian, some apps like gnome-boxes and Nautilus are not yet ready for Flatpak, or Flatpak is not ready for them yet. While I agree we should pursue that as a end goal, pulling out maintenance of JHbuild as tool for people to contribute to our modules before a viable alternative

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

On Sat, Jan 20, 2018 at 9:47 AM, Tristan Van Berkom wrote: > Instructions for using the gnome-build-meta BuildStream project can be > found at: > > https://wiki.gnome.org/Newcomers/BuildSystemComponent We found a bug in BuildStream which is triggered by

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

On Mon, Jan 22, 2018 at 9:13 AM, Florian Müllner wrote: Very much, I actually use a jhbuild GNOME session as my everyday system. I don't have a good answer. :/ Michael ___ desktop-devel-list mailing list

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

mcatanz...@gnome.org 於 西元2018年01月22日 21:34 寫道: > > > On Mon, Jan 22, 2018 at 7:25 AM, mcatanz...@gnome.org wrote: >> Were you actually using JHBuild to run integrated system components >> (gnome-shell, gnome-session)? If so, how? I was not aware that that >> was even possible nowadays. >> >>

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

On Mon, Jan 22, 2018 at 2:34 PM, wrote: > > > On Mon, Jan 22, 2018 at 7:25 AM, mcatanz...@gnome.org wrote: >> >> Were you actually using JHBuild to run integrated system components >> (gnome-shell, gnome-session)? If so, how? I was not aware that that was even >> possible

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

On Mon, 2018-01-22 at 07:34 -0600, mcatanz...@gnome.org wrote: > > On Mon, Jan 22, 2018 at 7:25 AM, mcatanz...@gnome.org wrote: > > Were you actually using JHBuild to run integrated system > > components > > (gnome-shell, gnome-session)? If so, how? I was not aware that > > that > > was even

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

On Mon, Jan 22, 2018 at 7:25 AM, mcatanz...@gnome.org wrote: Were you actually using JHBuild to run integrated system components (gnome-shell, gnome-session)? If so, how? I was not aware that that was even possible nowadays. When developing these components, Sorry, trying again When

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

On Mon, Jan 22, 2018 at 6:33 AM, Florian Müllner wrote: Is this information outdated? At least I see all those components in the gnome-build-meta repo, so I dare to hope ... You can build them, and there is CI to ensure the build does not fail. But I imagine it would

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

On Sat, Jan 20, 2018 at 6:06 PM, wrote: > When adding or removing a dependency from your > module, please now update gnome-build-meta instead. The BuildSteam page still mentions this: > In case you are trying to develop integrated components such as GNOME Shell, > GDM,

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

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

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

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

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

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

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

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

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

On Sat, Jan 20, 2018 at 3:47 AM, Tristan Van Berkom wrote: JHBuild --- For what regards the upcomming 3.28 release and further, patches should go to the gnome-build-meta project instead of the JHBuild modulesets - otherwise these patches would not be

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

Hi, The time has come, the Release Team is now maintaining the GNOME releases in BuildStream format, which is now available at: https://gitlab.gnome.org/GNOME/gnome-build-meta This repo is intended to contain the build metadata required for building the GNOME core modules only, while many