Roundcube pulls in apache as a dependancy while roundcube can also work on nginx with fastcgi and php. It may be better to have an apache2 useflag and an nginx use flag for roundcube.
Roundcube doesn't have apache as a direct dependency. Instead, it pulls virtual/httpd-php, and that has a dependency on any of the following: * dev-lang/php[apache2] * dev-lang/php[cgi] * dev-lang/php[fpm] So, if you have php[cgi] or php[fpm] emerged (necessary for e.g. nginx), it shouldn't pull apache.
virtual/httpd-php
I tried USE="-apache2" emerge roundcube and it told me I needed to enable the apache2 use flag.
(In reply to comment #3) > I tried USE="-apache2" emerge roundcube and it told me I needed to enable > the apache2 use flag. Indeed! I set php[-apache2] in package.use: The following USE changes are necessary to proceed: #required by virtual/httpd-php-5.3, required by mail-client/roundcube-0.7.2, required by roundcube (argument) =dev-lang/php-5.3.10 apache2 I expected it to suggest all three.
I looked at the ebuild for roundcube it does not mention apache. I think it may be in one of the PEAR ebuilds. I'll take a look--shall we mark this bug as confirmed?
(In reply to comment #5) > I looked at the ebuild for roundcube it does not mention apache. I think it > may be in one of the PEAR ebuilds. I'll take a look--shall we mark this bug > as confirmed? It's virtual/httpd-php that's pulling apache in.
(In reply to comment #6) > > It's virtual/httpd-php that's pulling apache in. To clarify: It's not pulling apache directly, but makes you set one of several PHP USE flags, the first of which is 'apache2'. It looks to me like portage only suggests the first USE flag that would satisfy the requirement.
So how do we fix this?
There is nothing here that needs to be fixed. Add fpm to the php USE flags and you should be good.
