On 05/11/2012 11:08 PM, Marvin Renich wrote: > For clarity, the etc-overrides-non-etc model that I am talking about is > where the file in /etc can override individual values, not where the > file in /etc must replace the entirety of the non-etc configuration. > This case is much much more acceptable to me. I wouldn't see any problem with it. I just don't want that new configuration values to be silently ignored upon upgrades, that's all I'm saying.
Thomas -- 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/4fad3cb8.1080...@debian.org