Re: upgraded config files in /lib/systemd/system
- Date: Mon, 6 Mar 2017 18:51:06 +0300
- From: Reco <recoverym4n@xxxxxxxxx>
- Subject: Re: upgraded config files in /lib/systemd/system
On Mon, 6 Mar 2017 14:25:44 +0000
Jonathan Dowland <jmtd@xxxxxxxxxx> wrote:
> On Tue, Feb 28, 2017 at 10:25:52AM -0500, Marc Auslander wrote:
> > IIRC in the "old" world, if you had a modified version of a config
> > file and an update modified the original released version, you got
> > a warning and a dialog which let you decide how to proceed.
> This is still the case on Debian systems: it's the "conffile" feature
> of Debian packages.
> Unfortunately systemd was designed in part around limitations of other
> systems' package managers, such as RPM, which lack this feature. So
> they invented the /etc/systemd/system-overrides-/lib/systemd/system
> override scheme instead.
To be more precise, a file in RPM actually *can* be declared as a
configfile (rpm -qc). It's 'dialog' part aka debconf that's
deliberately missing there.
Since both RPM install and upgrade do not allow user input by
design, user-modified configfiles are preserved as is (usually),
rpm-provided configfiles are placed nearby with .rpmnew extension.