On Mon, Jun 20, 2005 at 09:06:11PM -0500, Manoj Srivastava wrote: > On Mon, 20 Jun 2005 19:58:40 -0500, Manoj Srivastava <srivasta@debian.org (va, manoj)> said: > > On Sat, 18 Jun 2005 18:55:33 +0200, Miguel Gea Milvaques > > <debian@miguelgea.com> said: > >> Hi, On policy 11.5.4 says: "Web Applications should try to avoid > >> storing files in the Web Document Root. Instead they should use the > >> /usr/share/doc/package directory for documents and register the Web > >> Application via the doc-base package." > >> and in policy 12.3 says: "Packages must not require the existence > >> of any files in /usr/share/doc/ in order to function." > >> This points that all web applications that uses > >> /usr/share/doc/package directory are breaking policy 12.3, so I > >> think policy 11.5.4 must recommend other different directory. > > I agree with this assessment. > >> Recent works on webapps-common alioth project recommends to use the > >> directory /usr/share/PACKAGE/www. > > As others have suggested in this thread, since this is web > > application data meant to be served by this host, it makes sense to > > have a per-package sub director somewhere under /srv. > > /src/webapps/PACKAGE, perhaps? Or is the draft Web > Arrgh. /srv/webapps/PACKAGE, I meant. AFAICT, the FHS specifies that the structure of /srv is site-defined; and we already have a directory for static content, whether it belongs to webapps or not, which is /usr. Why would we want to move the canonical location of the packages' files to /srv in the total absence of standardization (or rather, in opposition to the standardization that exists for this directory)? -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature