I agree, web apps package are not standardized at all, there is a lot of things to say ... you pointed out database configuration problems, but there is others : * all packages enforce users to use subdirectories for apps you install. I mean : http://your_fqdn/app1/, http://your_fqdn/app2/ ... where a lot of users would like to use vhosts naming conventions like : http://app1.fqdn/ * some package even don't setup sql databases * wwwconfig-common is a good idea, but is not as good as it should/could be I'm interested in working about some policy about web applications packaging. (please note that I'm not a DD yet, only in the NM queue waiting for an AM, but I'm packaging flyspray) -- Pierre Habouzit http://www.madism.org/ -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- gpg : 1024D/A1EE761C 6045 409E 5CB5 2CEA 3E70 F17E C41E 995C C98C 90BE spam: mad.junk@madism.org
Attachment:
pgpTJA9WkqEE6.pgp
Description: PGP signature