After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 724235 - Make it possible to build against stable releases' API
Make it possible to build against stable releases' API
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Mac OS
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-02-12 12:55 UTC by Bastien Nocera
Modified: 2014-02-13 16:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2014-02-12 12:55:01 UTC 
Fedora ships snapshots of development releases, instead of stable releases. As there are no releases at all during the development process (or too late during that process for some distributions), it makes it hard, as a Fedora user to check that new features added to gnome-control-center's Network panel won't break the build for users on the stable version.

GTK+ has a few useful macros to handle this case, and more easily target specific versions of GTK+, or allow building against newer releases, but targetted at older ones.

Amongst them are:
- GTK_CHECK_VERSION
-  GDK_VERSION_MIN_REQUIRED
and GDK_VERSION_MAX_ALLOWED

This would allow us to test compiling against older releases (say, 0.9.8.x versions) when actually using a newer version.
Comment 1 Dan Winship 2014-02-12 18:31:10 UTC 
see danw/versioning (in both NM and nm-applet)

(this also includes an unrelated fix to make better use of glib's versioning macros)
Comment 2 Dan Winship 2014-02-13 16:26:47 UTC 
ok, there's now NM_VERSION_MIN_REQUIRED and MAX_ALLOWED, and by default, MAX_ALLOWED will be NM_VERSION_0_9_8, meaning gnome-continuous should already be starting to spew build errors...