Hey Dan, On Fri, 2014-02-07 at 11:35 +0100, Dan Winship wrote: > On 02/07/2014 09:24 AM, Bastien Nocera wrote: > > Heya, > > > > We're running into trouble with the recent "Team" support in GNOME, as > > there's no backing NetworkManager release with the necessary team > > support: > > https://bugzilla.gnome.org/show_bug.cgi?id=723769 > > The bug also mentions geoclue requiring libnm-glib 0.9.9.0, but I don't > see any obvious reason why it should from the sources...
That seems bogus indeed, I'll check with Zeeshan. > > It wouldn't be that much of a problem if Fedora didn't ship git > > snapshots of the "next" NetworkManager version. Why ship git snapshots > > in Fedora that are apparently not good enough for full releases? > > Because all of the NM maintainers are also Fedora developers, and so if > bugs show up, we can fix them quickly. Right, this also makes it problematic when new features are added to gnome-control-center (by NM developers, or other Fedora users such as myself) that require newer versions of NetworkManager. I don't think it would be such a problem if stable versions of Fedora used stable versions of NetworkManager. But having a git snapshot shipped in the stable release, when no other distribution gets to ship that snapshot is a bit bizarre in terms of release management (hence the subject of this thread). > I guess we should start hiding unstable APIs behind #defines so that > Fedora users don't accidentally depend on them. Something like GLIB_VERSION_MAX_ALLOWED would be very useful indeed, and would help curb those problems. Cheers _______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
