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. > /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. Also, it may be desirable to symlink the man page from /usr/share/man > 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 Amanda Waite wrote: > Attached is a draft Arc Case for Lighttpd integration into Solaris. I > notice that many Arc cases say "into Solaris" and not "into > OpenSolaris" or "into Nevada" or "into SXCE" and I'm not sure what the > correct choice of words is. > > This is my first Arc Case so please feel free to tear it to shreds. > I've done a good amount of due diligence in preparing this, but there > are certainly things that I've missed and things that I've probably > just got plain wrong. > > Thanks > > Amanda > > ------------------------------------------------------------------------ > > _______________________________________________ > > > webstack-discuss mailing list > webstack-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss
