[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Silly Packaging Problem



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 8 Aug 2006, at 10:48 pm, martin f krafft wrote:

also sprach Michael S. Peek <peek@tiem.utk.edu> [2006.08.08.2239 +0100]:
The next time there's an upgrade for courier-authdaemon, won't it
overwrite my version of /etc/courier/authdaemonrc with it's own?

No way. Packages must *never* overwrite your files in /etc.

Is this kind of thing addressed in the Debian Policy Manual (and
I just missed it)?

Well, yes. Section 10.7.

PS: I suggest you look into cfengine2 or parrot, these are designed
to do configuration file changes in an organised fashion. They have
steep learning curves but they're powerful. Doing this with packages
(c.f. dpsyco) is painful, IME.

I second the cfengine2 recommendation. We're managing configuration of around 1000 Debian machines here with it (700 or so IBM blades, 300 or so desktops, and a handful of other more exotic machines, some of which are not using Debian), and for the most part it works like a charm, although it does cause some problems when updating packages, because of course the cfengine-distributed conffile has a different md5sum which will cause dpkg to wibble. However, since we're managing conffiles with cfengine2, we just tell dpkg to always keep the existing config file, and that's OK, although it does mean we occasionally have to manually look at .dpkg-new files in case there's some new option we need to add.

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iQEVAwUBRNndqBypeFo2odvPAQItrAf/Qx4kdd3KMlECpmlZcDMhEFedHi20GBCe
2Z94gjTS5k17NBEMNPhHDs4bvSwz5wpj5/NJ+wuEkAZO8WMz2ZD+EJYimKJYIcMA
T0EREjWrtWDBFVLK/TRjt3VNkHBmvJKJHSTdihAVwpPRLGb6z50PucLzpPrUwr1C
cXjUvsgcEMDZQCcj9j4xNRPgUseqZsomvw6TIrmUByOkl/OCVOpKaTcHRbea+/Y9
Bn+Q4BzxE2N7zf0Kbw3tL1qqeEetklu7gFojAYLcAXr3p9px9bx4AeTkLbTLK9x8
9Famx1nAGgligiLYLXA/qYrdxNhYMB8Su40snzVCGRxP4g6XAADNAQ==
=uEMy
-----END PGP SIGNATURE-----



Reply to: