Per-Product Config file divergence

Björn Persson bjorn at xn--rombobjrn-67a.se
Tue Mar 11 00:45:23 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Stephen Gallagher wrote:
> /etc/somefile.conf is a [soft|hard]link that points to one of:
> 
> /etc/packagename.conf/default/somefile.conf
> /etc/packagename.conf/cloud/somefile.conf
> /etc/packagename.conf/server/somefile.conf
> /etc/packagename.conf/workstation/somefile.conf
> 
> Edits to somefile.conf would change whatever's on the other end of the
> link. The alternatives system would change this linkage, to another
> version, but switching it back will give you your edits, not just the
> original defaults.

I would prefer to have that mechanism under /usr/share, owned by RPM and
untouched by admins, and then a single /etc/somefile.conf, empty by
default (or with only comments) where admins can override the parameters
they need to, and only those. Then the admin's overrides would remain
effective when the link is changed.

But then the program that is to read the configuration file must be able
to handle such a setup.

Björn Persson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCgAGBQJTHlzFAAoJEOE4WtzWSuY/TA0P/0qaZ52Z3ZyZ0xn/+H+DRCOl
SPaFT2h8asuDgn/NooHbfU1KYdyaTmsJgGmSbk50e0nko8uRkzwlWZc7OxHUNU0Q
P63Ml0iIBJVFHFAXnt7MpU7AvCdX3wsm9V10JHGts539k9mHmP/r2GlkUn11n3RG
cVdMFGRPAydmfX6WRoxNjpBEgPJCG2T1eBwv7M8O0E8r/uhLlarCMVzkfTCqkYG4
cZ7k48kJ/FVPTrt/SMsDgXr9wYp3sdxKL0xnMpaXsc9lsqB4t5BqIJwsfbkK9qkp
V4xcLKD2zM1wbDL2aTqgDgXC5kFSxJZcXaY0JEVMRED0C+bJaqva8yJ/IGm4XE3b
Fovjc+JR3DHUHcSmc2/Cbsasf/6HcB5we5FP68U4owAdBFNnnGjVTFth0mEjcfnD
RnQv3K7pW7GkjWhTJkmQ8xou+D081jlTRMI3GkWx0gAbyDNCFdWwaMmHaB5QaitS
9yNJ3aoohd9fe3DhyC7W3WWl1PbVV60M0y51ruJMh0qPT5m5yPHLgtBCHsINqnhr
gN16VcbKYYv5IpWc5/3D/zPp4HVUmU4O6vl+agSzZhI1hyf/y7REj0vt311quDPK
QulUdyo++Gp8+hexS7vY5mnyYVGTR6Vp+rCAsv8CmXxOipBaAuJiKaqNKaCUp0Vz
2emHNqVrMSu/WFLshORW
=kp2a
-----END PGP SIGNATURE-----


More information about the devel mailing list