m...@linux.it (Marco d'Itri) writes: > On May 11, Nikolaus Rath <nikol...@rath.org> wrote: > >> > Wrong: since you have to copy the whole file to override it, and files >> > in /lib have no conffiles handling, after an upgrade you will not know >> > what was changed by you and what was changed upstream. >> I think everyone here agrees with that. The interesting case is when >> files in /etc/ can either explicitly include the /lib file, or >> implicitly override the /lib settings. > I do not know about any package which work this way,
Well, systemd has been mentioned one or two times here in the last weeks. > but there is any > then the problem is not different from packages which support multiple > configuration file fragments in /etc, ship the default configuration > in /etc and allow it to be modified by other configuration fragments in > /etc (e.g. Apache). I agree, and therefore I'm surprised that some people are getting so aggravated about this if the default configuration is installed in /lib rather than /etc. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762c27shc....@inspiron.ap.columbia.edu
