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

Re: RFC: OpenRC as Init System for Debian

]] Gergely Nagy 

> Tollef Fog Heen <tfheen@err.no> writes:
> > ]] Uoti Urpala 
> >
> > Hi,
> >
> >> Wrong: as mentioned in this thread before, one of the advantages of the
> >> etc-overrides-lib model is the option of having a file in /etc that
> >> first includes the one in /lib, then overrides just one particular
> >> value. This allows handling more updates without needing manual changes,
> >> as you can automatically pick up other updated values while keeping the
> >> override, without needing to do 3-way merges.
> >
> > This doesn't always work, though.  For instance, for systemd, you'd have
> > no way to get rid of an ExecStartPre line, since you can have multiple
> > of them.  It's probably not that common, but it's a use case I want to
> > support.
> In that case, the including file can be changed (by the admin) to be a
> separate file, that does not include, and get the usual conffile
> conflict dpkg prompt.

How would that work?

I have /lib/systemd/system/foo.service and want to change something in
it, I then create /etc/systemd/system/foo.service with a copy of the
/lib one plus whatever changes I want.

The version in /lib is then updated.  How is the admin notified?

(This is the problem I want to fix with some yet unwritten tool.)

Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Reply to: