Re: Removing web server dependencies from web apps
-----BEGIN PGP SIGNED MESSAGE-----
On 06.01.2012 10:12, Tanguy Ortolo wrote:
> The database server used by a given piece of software can be installed
> on another system. The Web server cannot.
Actually it can. Many modern webservers, including one I am maintaining
support CGI offloading and load balancing .
However I'd yet disagree with Thomas. Yes, his scenario is feasible and
a perfect use case for equivs, but I do not think, we should generally
drop dependencies to web servers because of that.
I personally do not get, why we do need packages of web applications at
all, but apparently other people do. Yet I do think, users of such
packages expect us to setup a working instance, just like we do for
almost every other package. We just can't provide a scenario which fits
all and generally I think, people using advanced setups like chroots and
CGI offloading are expected to know how to workaround such problems then.
>> But since I would install these packages in the chroot template, I *do
>> not* want to install apache there. The result is that I can't install
>> popuplar packages like wordpress, gallery, phpbb3 and so on, unless I
>> rebuild them and remove the "apache2 | httpd" dependency. I suspect that
>> I wouldn't be the only one with the issue.
It has been said before: Provide a httpd-cgi and a httpd package in your
chroot, and all is good.
>> Remember that a strong dependency is *forcing* users to install things,
>> and when, like here, it's going the wrong way for what one would do,
>> it's just *bad* (tm).
> No it is not. Using a package-based distribution that could take care of
> dependencies and not using that feature is, however.
Agreed. My bottom line is, the overall benefit of depending on a web
server for a web apllication is higher than working in special case
scenarios we - as a distribution - do not support just because we can't.
That has already been said before, so this argument is a bit redundant.
>> So, my suggestion would be to actually *remove* the dependency to the
>> web server (and move it as a Recommends: if you see fit...). I would
>> strongly advocate for this as being written in our beloved policy.
Why would web applications be the only exception of the rule? I'm sure
there are many more special case scenarios where a weaker dependency
would be better, but the overall benefit is more valuable. In fact, we
do have "Depends" at all then? I'm sure there is a special use case for
almost every dependency where it would be better not to have it at all.
with kind regards,
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----