gtk changes in the jhbuild moduleset

2016-10-07 Thread Matthias Clasen
Hi, we are getting ready to start development of gtk 3.90 in master. To avoid causing lots of breakage and irritation, here is the plan: 1) Switch the modulesets to use the gtk-3-22 branch for the gtk module 2) Rename the gtk module to gtk3 3) Add a gtk4 module that follows master 4) Switch appli

Re: gtk changes in the jhbuild moduleset

2016-10-07 Thread Bastien Nocera
On Fri, 2016-10-07 at 06:33 -0400, Matthias Clasen wrote: > Hi, > > we are getting ready to start development of gtk 3.90 in master. > To avoid causing lots of breakage and irritation, here is the plan: > > 1) Switch the modulesets to use the gtk-3-22 branch for the gtk > module > 2) Rename the g

Re: gtk changes in the jhbuild moduleset

2016-10-07 Thread Matthias Clasen
On Fri, Oct 7, 2016 at 6:36 AM, Bastien Nocera wrote: > On Fri, 2016-10-07 at 06:33 -0400, Matthias Clasen wrote: >> Hi, >> >> we are getting ready to start development of gtk 3.90 in master. >> To avoid causing lots of breakage and irritation, here is the plan: >> >> 1) Switch the modulesets to u

Re: gtk changes in the jhbuild moduleset

2016-10-07 Thread Simon McVittie
On Fri, 2016-10-07 at 11:14 -0400, Matthias Clasen wrote: > On Fri, Oct 7, 2016 at 6:36 AM, Bastien Nocera > wrote: > > Which would mean nothing called "gtk+" in the modulesets? Why not > > keep > > either gtk 3.x or gtk 4.x with that name? > > > > I'd expect the "gtk+" module to build GTK+ 4.x (

Re: gtk changes in the jhbuild moduleset

2016-10-07 Thread Matthias Clasen
On Fri, Oct 7, 2016 at 11:47 AM, Simon McVittie wrote: > On Fri, 2016-10-07 at 11:14 -0400, Matthias Clasen wrote: >> On Fri, Oct 7, 2016 at 6:36 AM, Bastien Nocera >> wrote: >> > Which would mean nothing called "gtk+" in the modulesets? Why not >> > keep >> > either gtk 3.x or gtk 4.x with that