Having the hard dependency for apache is not necessary as www-apps/mantisbt is depending on virtual/httpd-php already, which should pull in Apache (or whatever httpd the user wants to use, such as lighttpd). Reproducible: Always Steps to Reproduce: 1.Try to emerge www-apps/mantisbt 2. 3. Actual Results: www-apps/mantisbt tries to pull in www-servers/apache. Expected Results: www-apps/mantisbt should not pull in www-servers/apache
We do have the new virtuals available and the ebuild should be modified to use them. The suggested diff would be: --- mantisbt-1.0.8.ebuild 18 Nov 2007 08:45:29 -0000 1.5 +++ mantisbt-1.0.8.ebuild 10 Dec 2007 07:18:02 -0000 @@ -16,7 +16,7 @@ KEYWORDS="amd64 ppc x86" RDEPEND=" - www-servers/apache + virtual/httpd-cgi virtual/httpd-php !bundled-adodb? ( dev-php/adodb ) "
Gunnar, but what do you think if we just nuke www-servers/apache from DEPEND? We have virtual/httpd-php there, and seems that it pulls apache when necessary. Is that correct (and that's what OP asked about IIUC)? BTW, do we have other httpd-php providers beside apache?
virtual/httpd-php is provided by dev-lang/php and will not pull in apache. So I think depending on a CGI-capable webserver would be the right thing to do.
Why doesn't virtual/httpd-php pull in the httpd? The name would imply that it would pull in a php-capable (either through fastcgi or plugin (i.e, mod_php)) httpd, not just the php interpreter. That's how the rest of the virtual/httpd-* packages work. In the mean time, I believe having www-apps/mantisbt depend on virtual/httpd-php and virtual/httpd-cgi should do.
@Nick: Check the comment to the PROVIDE stanza in dev-lang PHP. Portage does not allow PROVIDE to be linked to use flags. And as long as you don't activate the "apache2" use flag the php ebuild won't pull in apache.
Thank you Nick, for report and Gunnar for suggested solution. If we have apache2 in USE flags then php pulls in apache2 and httpd-cgi will be satisfied with that. If not, we should install some cgi web server to serve our needs. Fixed.
