Thanks for the comments. Replies inline. Prashant Srinivasan wrote: > Amanda, > > > Lighttpd is delivered as the SUNWlhttpd package > > We will need a SUNWlhttpdusr and a SUNWlhttpdroot package at least, to > cover the files that go into /usr and /var. I'm not sure if the /etc > artifacts need another package for them - I'm guessing not. Since the > /usr and /var separation probably happens for sparse root zone support. > MySQL will be a good example to look at here. > I'll look at what others have done here. SUNWlhttpdroot will be a very "light" package.
> > /usr/sbin/lighttpd > > You may get asked about the choice of /usr/sbin as a home for the > lighty executable . . . since non-system applications usually make it > into /usr/bin. > I did feel that it should go into /usr/bin until I saw that all of the other binary distributions that I've seen install the Lighttpd binary to sbin in $PREFIX. /usr/local/sbin (sunfreeware), /opt/csw/sbin (blastwave), /opt/coolstack/lighttpd/sbin and even /usr/sbin in the case of Ubuntu > Also, it may be desirable to symlink the man page from /usr/share/man > I'll add this, it did seem odd to me at the time I wrote it. > >> Lighttpd has no obvious history of any interface instability and has been >> rock solid since we've worked with it (v 1.4.15) >> > > > I think the section interface stability section refers to stability of > the definition, not the presence/absence of bugs in the implementation. > I may be wrong here though. Good to check other ARC cases here. > -ps > I guess I wrote this badly, I meant rock solid in that they haven't kept changing the interfaces with every minor release Amanda
