James Carlson wrote: > Danek Duvall writes: > >>> They do it presumably for the same reasons several of the OpenSolaris >>> project teams have felt the need, which is to provide stability within a >>> given major release family while at the same time making the >>> newer-generation apps available. >>> >> I'd like to take the "presumably" out of that. If there's a real need for >> the versioning, let's hear it. If there isn't, let's not do it. >> > > Having the path to the configuration files moving around from build to > build like Robert Brown's pollen grains is distinctly not helpful for > users. > > Please don't bake the version number into the path unless we _really_ > need it, and then do only the minimum distinction necessary to make > sure that the incompatible universe-has-changed transitions are > accomodated correctly. > >
I've been thinking about the options, a single config file shared between multiple versions won't work if the user wanted to run more than one release simultaneously. If she copies the original and modifies it for use with the later version, she'd also have to modify the SMF method script for that later version. You would really need a separate config file delivered with each new Lighttpd release and an SMF method script that was setup accordingly. So would it be ok to deliver a versioned config file? say, lighttpd14.conf . It doesn't exactly address your issue, as it's not a whole lot different than providing a separate directory. Thanks Amanda
