On Tue, Jun 21, 2005 at 02:12:56PM +1000, Ben Finney wrote: > So we have:
> - static content goes somewhere under /usr/ > - static, platform-independent content goes somewhere under > /usr/share/ > - static, platform-independent content for PACKAGE goes under > /usr/share/PACKAGE/ > - some policy for specifying the location of web-served content of > PACKAGE is needed > - maybe /usr/share/PACKAGE/SOMETOKEN/ > where SOMETOKEN is 'web' or 'webapp' or 'www' or whatever > - service-published content goes somewhere under /srv/ > - /srv/ is site-defined > - thus shouldn't be clobbered by the package manager > That last one's a bit of a blocker, isn't it? We can put stuff in > /usr/share/PACKAGE/SOMETOKEN/ without worries. But how can we set up > a web application so it's ready to go, if the right place to publish > from is not writable by the package manager? Yes, there's the rub. I think there's room for moving forward on this point, I just don't think that editing policy is the place to start; nor do I think this particular policy bug has anything at all to do with /srv, because you don't want the files belonging to the packages themselves to be affected by whatever local policy the site admin chooses to impose on /srv. First, someone should show that it is possible to structure /srv for publishing without aggravating people currently using Debian, and only then should we discuss making it part of policy or moving package files there by default. > We could pass the question back a level: where should Apache, et al, > be looking for their web content? How can we tell Apache to look under > /srv/www/ if that directory is site-defined? Telling apache to look there doesn't clobber any contents set up by the site admin, does it? It's just a configuration default, which can be changed. -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
