(→Directories where all config files are read: new section) |
|||
| Line 4: | Line 4: | ||
More concretely, there are currently two packages NetworkManager-config-server (which contains the server-specific /etc/NetworkManager/conf.d/00-server.conf) and NetworkManager-config-connectivity-fedora (which contains the more-or-less desktop-specific /etc/NetworkManager/conf.d/20-connectivity-fedora.conf). But every file in /etc/NetworkManager/conf.d/ gets read, regardless of name, so it would not be possible to merge those files into the main NetworkManager package using the rules given here. (Which we probably don't want to do anyway, but there are probably other packages with similar file naming issues.) | More concretely, there are currently two packages NetworkManager-config-server (which contains the server-specific /etc/NetworkManager/conf.d/00-server.conf) and NetworkManager-config-connectivity-fedora (which contains the more-or-less desktop-specific /etc/NetworkManager/conf.d/20-connectivity-fedora.conf). But every file in /etc/NetworkManager/conf.d/ gets read, regardless of name, so it would not be possible to merge those files into the main NetworkManager package using the rules given here. (Which we probably don't want to do anyway, but there are probably other packages with similar file naming issues.) | ||
--[[User:Danw|Danw]] ([[User talk:Danw|talk]]) 14:00, 5 May 2015 (UTC) | |||
Revision as of 14:00, 5 May 2015
Directories where all config files are read
What if the config file goes into a directory where all files get read (or where all files starting with "foo" and ending with ".conf", etc, get read).
More concretely, there are currently two packages NetworkManager-config-server (which contains the server-specific /etc/NetworkManager/conf.d/00-server.conf) and NetworkManager-config-connectivity-fedora (which contains the more-or-less desktop-specific /etc/NetworkManager/conf.d/20-connectivity-fedora.conf). But every file in /etc/NetworkManager/conf.d/ gets read, regardless of name, so it would not be possible to merge those files into the main NetworkManager package using the rules given here. (Which we probably don't want to do anyway, but there are probably other packages with similar file naming issues.)