Re: [gtk-osx-users] Support of Older OS X Versions

2016-02-23 Thread philip . chimento
On Tue, Feb 23, 2016 at 10:40 AM John Ralls wrote: > Christoph's email about pango modules and gtk-mac-bundler reminded me of > another issue: GLib 2.46 includes an implementation of GNotification that > uses NSNotificationCenter, available only in OS X 10.9 and later. > > How important is it to

Re: [gtk-osx-users] Support of Older OS X Versions

2016-02-23 Thread Allin Cottrell
On Tue, 23 Feb 2016, Miroslav Rajcic wrote: How much testing it gets would depend on how many people use it, as does how much maintenance it gets. Understood, but hopefully at least Allin will test it other than myself :-) Actually, I'm sort of an oddity, in that I cross-build my GTK/OS X

Re: [gtk-osx-users] Support of Older OS X Versions

2016-02-23 Thread Miroslav Rajcic
> How much testing it gets would depend on how many people use it, as does how > much maintenance it gets. Understood, but hopefully at least Allin will test it other than myself :-) Regards, Miroslav ___ Gtk-osx-users-list mailing list Gtk-osx-user

Re: [gtk-osx-users] Support of Older OS X Versions

2016-02-23 Thread John Ralls
> On Feb 23, 2016, at 11:44 AM, Miroslav Rajcic wrote: > >> I guess there's another option available: Freeze your gtk-osx repo and >> change your application moduleset to include the locally-installed >> gtk-osx.modules instead of the online >> one, or we could add a moduleset that freezes gl

Re: [gtk-osx-users] Support of Older OS X Versions

2016-02-23 Thread Miroslav Rajcic
> I guess there's another option available: Freeze your gtk-osx repo and change > your application moduleset to include the locally-installed gtk-osx.modules > instead of the online > one, or we could add a moduleset that freezes glib at 2.44 and any dependent > packages at the last version tha

Re: [gtk-osx-users] Support of Older OS X Versions

2016-02-23 Thread Allin Cottrell
On Tue, 23 Feb 2016, Miroslav Rajcic wrote: Hi John, do you ask this question for GTK 3.x only? I am very much interested in GTK 2.x supporting older versions of OS X too. Me too, but I think this ought to be a moot point, since I don't suppose there will ever be a GTK 2 release that raise

Re: [gtk-osx-users] Support of Older OS X Versions

2016-02-23 Thread John Ralls
> On Feb 23, 2016, at 10:48 AM, Miroslav Rajcic wrote: > > Hi John, > > do you ask this question for GTK 3.x only? > > I am very much interested in GTK 2.x supporting older versions of OS X too. > I asked the users of my own program the same question, and I got a number of > users telling me

Re: [gtk-osx-users] Support of Older OS X Versions

2016-02-23 Thread Miroslav Rajcic
Hi John, do you ask this question for GTK 3.x only? I am very much interested in GTK 2.x supporting older versions of OS X too. I asked the users of my own program the same question, and I got a number of users telling me that they still use OS X 10.6.x. Regards, Miroslav

[gtk-osx-users] Support of Older OS X Versions

2016-02-23 Thread John Ralls
Christoph's email about pango modules and gtk-mac-bundler reminded me of another issue: GLib 2.46 includes an implementation of GNotification that uses NSNotificationCenter, available only in OS X 10.9 and later. How important is it to everyone here that we continue to support older versions?

Re: [gtk-osx-users] Removal of pango modules

2016-02-23 Thread Christoph Reiter
On Tue, Feb 23, 2016 at 7:21 PM, John Ralls wrote: > ISTM the last option, running create_pango_setup() iff the modules are > present, is the correct behavior. I'm no more enthusiastic about version > dependent checks in bundler than I am in configure scripts: They should be a > last resort onl

Re: [gtk-osx-users] Removal of pango modules

2016-02-23 Thread John Ralls
> On Feb 23, 2016, at 9:25 AM, Christoph Reiter > wrote: > > On Tue, Feb 23, 2016 at 3:50 PM, John Ralls wrote: >> Hooray! Bedhad said he was going to do that about 4 years ago. I guess it >> turned out to be harder than he expected. >> >> The problem with just whacking the code out of bundl

Re: [gtk-osx-users] crash on maximize/unmaximize

2016-02-23 Thread John Ralls
> On Feb 23, 2016, at 7:10 AM, Allin Cottrell wrote: > > On Sun, 21 Feb 2016, John Ralls wrote: > >>> On Feb 20, 2016, at 10:58 AM, Allin Cottrell wrote: > > [detailing a fix for crash on close-window-when-maximized on > OS X 10.11] > >> Thanks, I've pushed your patch to gtk-2-24, gtk-3-18,

Re: [gtk-osx-users] Removal of pango modules

2016-02-23 Thread Christoph Reiter
On Tue, Feb 23, 2016 at 3:50 PM, John Ralls wrote: > Hooray! Bedhad said he was going to do that about 4 years ago. I guess it > turned out to be harder than he expected. > > The problem with just whacking the code out of bundler is that there's no > real linkage between bundler versions and gtk

Re: [gtk-osx-users] crash on maximize/unmaximize

2016-02-23 Thread Allin Cottrell
On Sun, 21 Feb 2016, John Ralls wrote: On Feb 20, 2016, at 10:58 AM, Allin Cottrell wrote: [detailing a fix for crash on close-window-when-maximized on OS X 10.11] Thanks, I've pushed your patch to gtk-2-24, gtk-3-18, and master. Thanks, John. But at this point, as Joshua Pettus remarked,

Re: [gtk-osx-users] Removal of pango modules

2016-02-23 Thread John Ralls
> On Feb 23, 2016, at 1:35 AM, Christoph Reiter > wrote: > > Hey, > > pango 1.38 (which is required by gtk+ 3.18) no longer contains modules > which breaks the bundler (you might only notice this after a fresh > rebuild as the old modules stay around). The easiest solution would be > to kill a

Re: [gtk-osx-users] 10.11 bootstrap and python2 problems

2016-02-23 Thread Christoph Reiter
On Mon, Feb 15, 2016 at 6:22 PM, Christoph Reiter wrote: > On Mon, Feb 15, 2016 at 4:49 PM, Christoph Reiter > wrote: >> The second problem is python2 fails to build correctly. It complains about >> zlib/bz2 missing after make is finished and I'm also hit by the libxml2 >> linking problem [1] whi

[gtk-osx-users] Removal of pango modules

2016-02-23 Thread Christoph Reiter
Hey, pango 1.38 (which is required by gtk+ 3.18) no longer contains modules which breaks the bundler (you might only notice this after a fresh rebuild as the old modules stay around). The easiest solution would be to kill all code there specific to pango: * Update pango to 1.38.1 * Remove the Pyt