On Tue, Feb 28, 2012 at 5:59 PM, Seblu <se...@seblu.net> wrote: > On Tue, Feb 28, 2012 at 3:51 PM, Jelle van der Waa <je...@vdwaa.nl> wrote: >> On Tue, Feb 28, 2012 at 3:34 PM, Seblu <se...@seblu.net> wrote: >>> >>> On Sun, Feb 26, 2012 at 4:20 PM, Tom Gundersen <t...@jklm.no> wrote: >>> > On Sun, Feb 26, 2012 at 3:46 PM, Seblu <se...@seblu.net> wrote: >>> >> On Sun, Feb 26, 2012 at 2:56 PM, Tom Gundersen <t...@jklm.no> wrote: >>> >>> /srv is admin territory, similar to /home. No package should >>> >>> put stuff there. >>> >> Are you sure of this? >>> >> Currently many "http" packages use /srv/http to put static files. e.g >>> >> backuppc, flyspray, roundcube... >>> >> >>> >> >>> >> http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM >>> > >>> > The consensus seems to be that we don't let packages put stuff in >>> > /srv, so I thought it would make sense to let namcap reflect this. >>> Sure ! >>> >>> I just wondering what is the arch way of doing web package :) >>> > what's about adding /etc/webapps and /usr/share/webapps in php.ini ? > We already add /srv/http. > Looking inside repositories for examples, phpmyadmin look like an exception. We lack of clean rules and a cleanning of our web packages.
What's about a /var/lib/webapps to have "writable" content outside /usr ? Wiki suggest to symlink /var/lib to /usr/share/webapps? -- Sébastien Luttringer www.seblu.net
