On Thu, Jan 31, 2013 at 8:15 PM, Ulrich Pegelow <ulrich.pege...@tongareva.de> wrote: > Am 31.01.2013 08:00, schrieb Moritz Lipp: >> Hello, >> >> On 2013-01-31 07:28:49, Ulrich Pegelow wrote: >>> There is no definition of g_mutex_init in any include files here on my >>> system. My glib2 is of version 2.30, which is the current one for >>> OpenSUSE 12.1. I assume g_mutex_init() is only defined in newer versions >>> of glib2. >> >> Indeed, g_static_mutex_init has been deprecated since version 2.32 and >> therefore >> g_mutex_init has been introduced. >> > > Sure. But it's at least a change in philosophy if darktable insists on > the newest versions of central libraries, those that even quite recent > Linux versions don't have. > > OpenSUSE 12.1 is just the version one preceding the current one. It's > from November 2011 and I would not call it deprecated. I don't care if > we insist on the most recent versions of some special libraries. That's > easy to update for users. But there are so many dependencies for glib2 > that updating it, is equivalent to forcing users to always update their > Linux distributions. > > Frankly I would in any case try to avoid that. It's a hell of work and > will certainly break things and bring new problems in all places. > > So my question: what forces us now to deprecate all systems with glib2 > prior to 2.32? We should have good reasons for that step.
traditionally we used version macros to make everybody happy: src/common/image.c:945:#if GLIB_CHECK_VERSION (2, 26, 0) i don't see a reason why we shouldn't do it in this case. -jo ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel