Am Donnerstag, 21. April 2011, 14:39:13 schrieb Ludwig Nussel:
Ralf Lang wrote:
while packaging horde4 I noticed the rpmlint warning horde4.noarch: W: non-etc-or-var-file-marked-as-conffile /srv/www/htdocs/horde4/config/conf.php.dist
If config files are allowed to live in /var (where web apps used to live in old times) why are they not allowed in /srv ?
Good topic. Why do web apps not adhere to the traditional layout we are used to anyways?
Because the default suse apache server does not like access to arbitrary locations, I know of no policy on installing vhosts via rpm (or even assuming that apache is used and not another httpd). The Horde3 debian package used symlinking a lot to move configs to /etc/ but it actually lead the majority of users to NOT using the packages but installing pristine sources. I've been taking part in the upstream project's support channels, irc, mailing list and have experienced that a lot of users If we develop some common process for web app deployment (including a default running environment) I have no objections against /etc/. I am pretty sure that what happened to the debian packages would happen to the suse packages again otherwise.
/srv is a mess. It mixes vendor files with user files, config files with static data, binaries with state databases etc.
This is not specific to horde of course but let's use it as example. Why not keep the default document root /srv/www/htdocs clean and put horde to e.g. /usr/share/horde4, it's config files to /etc/horde4 and it's database or whatever variable data it has to /var/lib/horde4?
See above. Without actually providing a sane, fast-to-run solution we alienate users. -- Ralf Lang Linux Consultant / Developer B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org