m...@linux.it (Marco d'Itri) writes: > On May 10, Bjørn Mork <bj...@mork.no> wrote: > >> Agree. Copying a large set of default policies into /etc just because >> they *can* be overridden is not user friendly. And it does not make the >> defaults any more configuration either. It just hides important local >> changes and makes it difficult both for the user and the application >> itself to distinguish between defaults and configuration overrides. > > 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. It's not clear to me why such a system would be inferior to the current debian practice. 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/87ipg3ioga....@vostro.rath.org
