Re: Let's kill gnome-common!

On Tue, Feb 13, 2018 at 3:43 AM, Sébastien Wilmet wrote: The list is not complete, there is for example gedit as well, I think it was common to *not* list gnome-common as dependency in the jhbuild modulesets because libraries like gtk was already depending on it. Hm,

Re: Let's kill gnome-common!

On Tue, 2018-02-13 at 15:13 +0100, Frederic Peters wrote: > > On Tue, 2018-02-13 at 11:19 +, Emmanuele Bassi wrote: > > > Work is in progress to let maintainers upload tarballs with the > > > generate API reference for developer.gnome.org > > > > Hi, > > okay, how is that supposed to work

Re: Let's kill gnome-common!

Milan Crha wrote: > On Tue, 2018-02-13 at 11:19 +, Emmanuele Bassi wrote: > > Work is in progress to let maintainers upload tarballs with the > > generate API reference for developer.gnome.org > > Hi, > okay, how is that supposed to work in general? As Meson builds out of > the source

Re: Let's kill gnome-common!

On Tue, 2018-02-13 at 11:19 +, Emmanuele Bassi wrote: > Work is in progress to let maintainers upload tarballs with the > generate API reference for developer.gnome.org Hi, okay, how is that supposed to work in general? As Meson builds out of the source tree, is that "work in

Re: Let's kill gnome-common!

Emmanuele Bassi wrote: > > I do not want to steal the thread, but when talking about ports to > > Meson, would it make sense to finally fix the infrastructure to work > > with other than automake files too [1]? It's when generating the > > content for developer.|help.gnome.org. Considering that

Re: Let's kill gnome-common!

On 13 February 2018 at 11:17, Milan Crha wrote: > On Tue, 2018-02-13 at 09:33 +, Philip Withnall wrote: >> porting the build systems of those modules to Meson is another >> legitimate way to port away from gnome-common. It would be the better >> choice in the long run for

Re: Let's kill gnome-common!

On Tue, 2018-02-13 at 09:33 +, Philip Withnall wrote: > porting the build systems of those modules to Meson is another > legitimate way to port away from gnome-common. It would be the better > choice in the long run for modules we are going to be maintaining for > a while. Hi, I do

Re: Let's kill gnome-common!

On Mon, Feb 12, 2018 at 07:08:34PM -0600, mcatanz...@gnome.org wrote: > I want to remove gnome-common from our BuildStream projects, but a few > modules are still depending on it: gcr, gnome-autoar, libnotify, > adwaita-icon-theme, gnome-menus, and gsettings-desktop-schemas. The list is not

Re: Let's kill gnome-common!

Thanks Bastien. > Or better port to meson. Yeah that sounds like a better task. Carlos Soriano GNOME Board of Directors On 13 February 2018 at 10:20, Bastien Nocera wrote: > On Tue, 2018-02-13 at 10:08 +0100, Carlos Soriano wrote: > > Hi Michael, > > > > Could you give

Re: Let's kill gnome-common!

On Tue, 2018-02-13 at 10:08 +0100, Carlos Soriano wrote: > Hi Michael, > > Could you give some context and explanation on this? I could take the > gnome-autoar, but need to know why this is wanted and the alternative > to gnome-common. When the wiki comes back:

Re: Let's kill gnome-common!

On Tue, 2018-02-13 at 10:08 +0100, Carlos Soriano wrote: > Hi Michael, > > Could you give some context and explanation on this? I could take the > gnome-autoar, but need to know why this is wanted and the alternative > to gnome-common. Handily all written up a while ago:

Re: Let's kill gnome-common!

Hi Michael, Could you give some context and explanation on this? I could take the gnome-autoar, but need to know why this is wanted and the alternative to gnome-common. Cheers On 13 February 2018 at 02:08, wrote: > Hi, > > I want to remove gnome-common from our

Let's kill gnome-common!

Hi, I want to remove gnome-common from our BuildStream projects, but a few modules are still depending on it: gcr, gnome-autoar, libnotify, adwaita-icon-theme, gnome-menus, and gsettings-desktop-schemas. If you help fix these sad modules, you'll earn the right to say that you helped fix