2012/4/24 Jérémie Burtin <jere...@jeremieburtin.fr>: > On 24/04/12 15:54, Charlie Smotherman wrote: >> >> On Tue, Mar 27, 2012 at 2:11 PM, Jeremie BURTIN >> <jere...@jeremieburtin.fr> wrote: >> Jeremie, >> >> Thanks for the bug report. > > You're welcome. > >> Although Ampache is capable on running on just about any webserver, >> Ampache's packaging does not support the installation on nginx. The >> packaging only supports the installation on Apache2, Lighttpd and >> Mythbuntu. I consider installation on any other webserver a custom >> install. > > I am not asking for a nginx support, I just think that the installation > should not fail if the user is using another web server than apache2. > As for now, apache2 (and lighttpd) is only a recommendation. Ampache does > not depends on apache2, the package should then respect this.
yes but ampache does depend on libapache2-mod-php5 which will pull in apache2 even though the package does not directly depend on apache2 ampache-common would not care which webserver you are using because it would not have any dependencies (well it would depend on debhelper and maybe debconf) > > >> However with the upcoming Apache2.4 transition Ampache's packaging >> will only support Apache2. I am contemplating splitting the package >> into ampache-common and ampache-apache. >> >> Ampache-common would be for users such as yourself which want to use >> Ampache on webservers which are not supported in the packaging. This >> will also allow users to setup ampache in VM's, LXC's or what ever >> where the installation of a webserver in not desired. >> >> Splitting the package will also allow motivated community members to >> develop there own packages for their favorite webserver ie: >> ampache-nginx or ampache-monkey or ..... >> Trying to support multiple webservers has IMHO made the maintainer >> scripts overly complicated and splitting the package would >> significantly simplify the maintainer scripts. > > I think there should not be any web servers support. The user should be able > to install ampache, whatever he's webserver is. No ampache-apache2, no > ampache-nginx... Only ampache. The very best could be some example > configuration files (see redmine package, containing configuration files for > lighttpd, apache2, nginx... in /usr/share/redmine/example/). Then the user > can use it, or write his own configuration file. Then you would want to install ampache-comman and hack away to your hearts content. This is the idea behind ampache-common. No webserver, no config files, no debconf question, no symlinking to system libs, no setting up logging, no logrotation, **nothing**. The only thing ampache-common would do is install ampache into /usr/share/ampache/www per the webapps policy manual. Ampache-apache would be for users who are not that familiar with setting up mysql, php and apache2 (noobs) or lazy people such as myself who want to simply "apt-get install ampache" and just have it work. > > I sincerely hope you won't choose to only package ampache with apache2, > which would be a big pain for non apache2 users. Once again ampache-common would allow non apache2 users to setup ampache the way they want, with the webserver they want. Right now this is the only idea I have to satisfy both power users and noob's alike. Nothing is set in stone so I am open to suggestions. Best regards -- Charlie Smotherman Debian Contributor Ubuntu Developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
