On Fri, Sep 30, 2011 at 11:55 AM, Adam Nielsen <a.niel...@shikadi.net> wrote: > It is a limitation I think of any/every configuration control system.
Why can't it show the diff / update like dpkg does? >> The point is that it's not a perfect improvement. Having conf bits in >> more files means it's harder for a normal user to find/read/update all >> bits. > > That's true, but then in this case the user already has to find/read/update > the bits in the conf-available directory so one more split shouldn't come as > a surprise. By default no confs are enabled there. >> We do agree that (in principle) it would be nice to support stuff like >> Puppet better. >> So let's say we've got lighttpd.conf and platform.conf. Where would >> the ipv6 include go? I'd say platform.conf. >> Since you wanted to disable the ipv6 include, you'd have to modify >> platform.conf and you'd have the same problem as you do now, right? > > Not quite. Since enabling IPv6 support works the same on any distro, it > shouldn't go in the platform-specific section. I would say, as a rough Does it? The IPv6 code is Debian specific (AFAIK). > guide, anything you *must* change from the upstream lighttpd.conf to make it > fit into Debian (user/group, pidfile, etc.) would go into platform.conf, and > anything you change just to make it nicer (like IPv6 or the default module > list) can go into some other file. For example, I would only expect these > options to be in platform.conf: > server.upload-dirs = ( "/var/cache/lighttpd/uploads" ) > server.errorlog = "/var/log/lighttpd/error.log" > server.pid-file = "/var/run/lighttpd.pid" > server.username = "www-data" > server.groupname = "www-data" > compress.cache-dir = "/var/cache/lighttpd/compress/" Those are quite unlikely to change, so what benefit do you get from moving them to another file? Note that the main lighttpd.conf has already been minimized. > With a new daemon version yes, but with a security update or similar where > the version is unchanged it may not be necessary. Say for example you had > accidentally set the lighttpd user to root and the default document-root to > "/". The web server would still work and when the mistake is realised the > platform.conf could be easily updated to correct the mistake, without > requiring any config merging. Security (and stable) updates are unlikely to contain updated conf files. BTW, I've requested upstream to enable IPv6 by default or to provide a better/easier way to enable it. Unfortunately they didn't want to do this for 1.4. Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
