Jyri Virkki wrote: > Amanda Waite wrote: > > Not necessarily a question for this case, but is it possible for > future packages to deliver additional configuration into a known > location? For example apache2 packages can deliver .conf files into > conf.d. Thinking of the example above, that would allow you to later > deliver a package with appropriate dependencies and the corresponding > configuration such that it'll "just work" merely by installing the > package. > 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? >> The Lighttpd man pages are fairly sparse and don't cover all of >> command line flags. It would be good to add to them and contribute th >> back to the Lighttpd commons >> > > 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?
> > LSARC/2008/126 is "memcached 1.2.5 to be included in OpenSolaris > > > Hm, who is expected to read these log files? If they are private > nobody but the code itself is allowed to look at them, which doesn't > seem to make sense for a log file? > I've actually removed memcached from the list of imported interfaces as it was a requirement of mod_cml which we are not including support for. I've changed the "lighttpd log files" exported interface to be "uncommitted". Thanks Amanda
