MIkey wrote: > > Actually, if you emerge mod_php (yeah, I know, bad example) before emerging > apache, and apache2 is in your USE flags, it will emerge apache2 as a > dependency. So it does, in effect, install apache2. Depending on the > order you emerge packages, of course. I have not researched it, but it > would probably do the same thing for various webapps that use php.
This is exactly the intended behavior. Try this sequence of commands with the apache2 USE-flag disabled. emerge php (installs apache-1.3 and mod_php) emerge --update --deep world (--deep required as apache was installed via php, so isn't in world - now you have apache-1.3, apache-2.0, and mod_php, with mod_php only working with apache-1.3) yes, apache-1.3 and apache-2.0 are in different slots, but portage doesn't limit upgrades to the slot - it will see the 2.0 as a newer better apache and install it as well (all the slot does in the case of the upgrade is keep the old version around as well) This is why if you disable the apache2 USE-flag you need to also mask out apache-2.0 - otherwise, updates become unintuitive. I am not against removing the USE-flag as long as apache-2.0 is masked out, but I highly doubt this is what anybody wants, as it becomes even more complicated to now use apache-2.0. Also, if apache-2.0 is masked, many of the add-on modules would need to be masked out as well. It becomes a nightmare to manage all this (trust me, I've been there, being the apache maintainer!) -- Michael Stewart [EMAIL PROTECTED] Gentoo Developer http://dev.gentoo.org/~vericgar GnuPG Key ID 0x08614788 available on http://pgp.mit.edu --
signature.asc
Description: OpenPGP digital signature
