[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:
> > ]] Gergely Nagy 

> >> 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?
> NEWS.Debian, like with any significant default change.

So you won't get the dpkg conffile conflict prompt, then?  Can you
explain what the scenario you talked about would look like, since it's
apparently not the scenario I was thinking about?

> Other than that, the best I can think of is keeping track of what
> version of the package a default changed in, and triggering something
> from preinst, when upgrading from a version that is older than the
> change.

This is basically what the tool I'm suggesting to write will do.

> This however, requires a lot of manual work, might aswell shovel the
> whole thing from under /lib to /etc then, but then we still didn't solve
> the problem: suppose there is a unit file that supports starting
> multiple instances, by way of symlinking. I start to use this feature,
> I change nothing, just symlink files around. At some point, this feature
> gets removed, my upgrade succeeds, but my instances won't start anymore,
> and the best notification I have is something that scrolled by that a
> conffile was upgraded.

You'll get a notification, since the file will have changed, then.

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

Reply to: