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 706616 - rename 'system-connections' to just 'connections' /etc/NetworkManager.conf
rename 'system-connections' to just 'connections' /etc/NetworkManager.conf
Status: RESOLVED WONTFIX
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks: nm-next
 
 
Reported: 2013-08-22 21:22 UTC by Pavel Simerda
Modified: 2018-10-18 22:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proof of concept patch. (5.45 KB, patch)
2013-08-30 11:37 UTC, Pavel Simerda
none Details | Review

Description Pavel Simerda 2013-08-22 21:22:56 UTC
Rename 'system-connections' to just 'connections' /etc/NetworkManager.conf. It is pretty easy to do in a backward compatible manner. One approach would be to check the existence 'connections' directory and step back to the old name upon failure.
Comment 1 Pavel Simerda 2013-08-30 11:37:14 UTC
Created attachment 253598 [details] [review]
Proof of concept patch.

Adding a proof of concept patch. No warranty.
Comment 2 Dan Williams 2014-04-25 15:45:43 UTC
Yeah, we should probably do this.  Though for upgrade-ability, I think we need to read connections from both directories, but only save new connections in the new directory, right?
Comment 3 Thomas Haller 2016-01-20 13:51:53 UTC
moving to 1.4 as this won't be done for 1.2

(also, the problem is how to do it without too much hazzle and without breaking existing installations...). It seems hard to get right and no high priority.
Comment 4 Thomas Haller 2016-09-02 00:07:59 UTC
Yes, a better name would be nice. But I think this is involved with so much effort to preserve backward compatibility, that it is easier to stick with the current name.
Comment 5 Thomas Haller 2018-10-18 22:45:47 UTC
I am closing this as WONTFIX.

The problem is that this directories contains the keyfile files.
That means, simply changing it, would be a major breakage during package update. It would be essentially not manageable for a distribution to inflict such a pain on the users.

So, the only alternative would be to add a new directory and deprecating the old one. But that again is a huge effort and complexity, both to implement and to document.


In fact, we now are about to add additional directories like /var/run/NetworkManager/system-connections and /usr/lib/NetworkManager/system-connections.

While I personally argued for a better name at least for the new directories, it was decided that consistency of naming is more important than choosing the best name. I do see a point there.