On Fri, Dec 30, 2011 at 07:54:34PM -0800, Josh Triplett wrote: > The numerous upstreams which follow this model introduced it > specifically *because* of distributions and package management, which > they specifically had in mind as a design constraint. The "search path" > behavior, along with the consistent use of .d directories, allows a > clean distinction between upstream configuration, vendor/distribution > configuration (any changes Debian wants to make to the defaults), > sysadmin overrides of the defaults, and sysadmin configuration building > on the defaults, without forcing sysadmins to perform manual three-way > merges every time they upgrade. It also either (a) prevents upstream from ever changing that default or (b) silently breaks packages for the user. If option foo is set to bar in the upstream configuration and then upstream changes it to baz, the package breaks for the sysadmin. If the configuration were stored in /etc, the sysadmin would get notified by dpkg or ucf and would have an opportunity to change it. So the only sane thing to do is not change the default, ever. This does not sound to me like an especially robust model. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Attachment:
signature.asc
Description: Digital signature