Hi, On Sun, Nov 24, 2013 at 10:59 PM, scl <scl.gplus@xxxxxxxxx> wrote: > Hi, > > today there was [bugreport] about outdated builds for OSX. > > One reason for not being able to provide an official GIMP 2.8.8. > on OS X build were serious issues on OS X Mavericks, for instance > the [showstopper in the Text tool]. These have been solved in > the meantime (thanks especially to Simone Karin Lehmann, Michael > Natterer and Daniel Sabo). > > Therefore I think we should bring out GIMP 2.8.10 soon, > including an official OS X build (preferably also for some older > OS X versions). As far as I know Claytons build is at the ready. > All we need is a 2.8.10 bump, don't we? > > This situation shows us another weakness again: > there are at least four people working on an OS X release: > Clayton Walker, Simone Karin Lehmann, Partha Bagchi and > David Evans (Macports), not to mention the (still active?) maintainer > of the outdated Fink build and the various people building GIMP > on their own Macs. All of them do it in their rare spare time. > All of them struggle alone with the special build issues of GIMP > on OS X, its dependencies and the API incompatibilities between the various > OS X versions. > Can you guys and girls please find a way to work together? > What makes it so hard to speak to another at the mailing list or IRC > and unite your forces? Come on, we don't bite ;-) A little in-topic and off-topic about the Windows build! Could we make sure that all patches of third party that we know of are used for the official release this time? In particular, all relevant patches applied to the nightly build! Because the last GIMP 2.8.8 for Windows release still had bugs that were already fixed on the nightly builds. I see in particular 2 bugs related to fontconfig (there may be other patches I don't know of, better ask Drawoc and check the dir build/windows/jhbuild/patches/): - The conf.d path bug: https://bugzilla.gnome.org/show_bug.cgi?id=708110 Fixed either with patch in the repo: build/windows/jhbuild/patches/fontconfig-fix-config-dir.patch Or by using fontconfig >= 2.11.0 - Better fontconfig cache directory: https://bugzilla.gnome.org/show_bug.cgi?id=703331 Still in discussion upstream, but if we feel this is the way, we can already apply the patch available there: https://bugs.freedesktop.org/show_bug.cgi?id=71691 A small in-topic note, back to OSX build: Clayton Walker proposed to update the cache directory for the OSX build, but it has been rejected upstream: https://bugs.freedesktop.org/show_bug.cgi?id=71715 Well maybe all the OSX package maintainers and developers in our team could discuss this, and if they all agreed a change in fontconfig cache was in order for the OSX build, well you can configure it appropriately. Even though a change upstream is nicer, that's still only a configuration change, so we should do it. If that helped people, we can also organize a small release meeting? In any case, I really agree with Sven, that we can really improve the quality of our releases, whether on OSX (with package dispersion) or Windows (synchronisation with nightly and stable). Regards, Jehan > > Thanks in advance, > > Sven > > [bugreport]: > https://bugzilla.gnome.org/show_bug.cgi?id=715094 > > [showstopper in the Text tool]: > https://bugzilla.gnome.org/show_bug.cgi?id=711281 > _______________________________________________ > gimp-developer-list mailing list > List address: gimp-developer-list@xxxxxxxxx > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
