Jyri Virkki wrote: > Matt.Ingenthron at Sun.COM wrote: > >> On this item, with this integration could we define/deliver a package >> for the lighttpd default content? Perhaps something like >> SUNWlighttpd14u-content upon which SUNWlighttpd14u depends? >> > > That sounds worse to me, later that package needs to be made to disappear > and disown its content. >
Actually, it would just be replaced by a different package in a distro, wouldn't it? > Do you feel it is likely the branding packages will come to life in > the near future? If yes, it's better to not deliver an index file here > and live with an empty docroot for a couple builds. It'll be the > cleanest way to deliver the file from the branding package. > The direction we got from the OpenSolaris folks is that we should have branding packages per component. This means we need this package in order to enable branding by other distros. At first I had similar thoughts to yours, which is that there should be a single branding package. The problem with that is that it certainly wouldn't make sense to have a lighttpd index.html in most distros. Not every install will need to have all branding files and the directories certainly wouldn't need to be there. With IPS and software repositories, in many cases we have to be more, not less, granular with our packages. The "core" has gotten smaller. Unfortunately, I think we'll need a branding package for every component which may have separate branding and is not dependent on something else branded. The only other option is to deliver a component which will generate errors when run out of the box. - Matt -- Matt Ingenthron - Web Infrastructure Solutions Architect Sun Microsystems, Inc. - Global Systems Practice http://blogs.sun.com/mingenthron/ email: matt.ingenthron at sun.com Phone: 310-242-6439
