Amanda waite wrote: > > Yes it is possible to deliver additional config files in this way. I'd > need to better understand how the mechanism works in Apache2 and if it > could be applied to Lighttpd. Is this something we can look at for > future packages then?
You could do it in the future. Or you could definte the mechanism (location and inclusion rules) now and only later make use of it. Earlier is nicer than later, but your choice. > >Will you do that as part of the current work (maybe with Jan's help)? > >It'd be best for the man page to be complete & correct. > > > Yes, along with the Umbrella man page. Would the updated versions need > to be part of the Arc Case or is showing intent enough? It's nice if the full man page is part of the case, but IMO a committment to what will be done is enough for the moment. > I've changed the "lighttpd log files" exported interface to be > "uncommitted". Uncommitted is quite stable for the long term. Are these access log files using common log format (or similar standard format) in which case Uncommitted (or even Stable) might be correct? Or are these free-form strings for human consumption? If the latter, is there a guarantee they will remain constant so if I write a log file parser it'll continue to work across releases? Log files meant for human consumption only (not for scripts to parse) are typically classified as "Not An Interface" which means they're public, but not meant as a programmatic interface. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
