On Sat, 2015-09-12 at 19:56 +0200, Xen wrote: > Seriously I would suggest to get rid of the CamelCase name. It breaks > compatibility or congruency with a lot of other things and as a user you > are constantly wondering what the name is going to be. NetworkManager? > networkmanager? network-manager? It changes from situation to situation. > There is no reason for NetworkManager to be capitalized (least of all > the binary) because this is no user-friendly system where NM sits inside > some sort of pretty application catalogue. Linux packages are always > lowercased. Most Linux directories are lowercased (and they should be). > You have to follow convention. This only creates problems. This is not > Microsoft Windows where each program sits in C:\Programs or C:\Program > Files and where filenames are CASE INSENSITIVE. Even the KDE convention > to name the "Documents" and "Pictures" folders with upper cases creates > issue because of the case sensitivity, which means that "cd documents" > won't work. If you want this in Linux, you have to ensure that the > actual names are lower case, but that you create a representation in the > GUI (!!!) that is capitalized. I know other packages do this as well, > notably PackageKit and UPower, but it is bad habit and bad choice and > makes it harder for everyone, because most of what you do in Linux is > still done using the COMMAND LINE.
I happen to disagree, but everyone is entitled to their opinion. As it stands, the official name is "NetworkManager", but distributions apply their own packaging guidelines and some distributions disallow CamelCase names, but certainly not all Linux distributions. So distributions that choose to allow only lower-case names will then obviously create confusion between the package name and the project name. Dan _______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
