Michael Stewart (vericgar) wrote: > My point was missed. The USE-flag does not select which version of > apache to build. It tells the add-on modules (such as mod_php, mod_perl, > etc) which version of apache to build against. If apache2 is on, then it > depends on and builds against apache-2.0. If apache2 is off, then it > depends on and builds against apache-1.3. (Mind you mod_php is a bad
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. I would venture to guess that apache/php is the most commonly installed combination by people setting up web servers. Both of these require additional use flags be set, dev-lang/php won't even install correctly if you don't. The installer is going to have to either edit USE flags in make.conf or package.use anyway, so in my view apache2 should not be present in the (system) profile. I have no problem with apache2, it is bloating what should be strictly the system profile that I have problems with. I would like to be able to use an "official" gentoo profile without having to add a buttload of -xxx USE flags... Obviously I fall into Patrick's "minimalist" category. Apache2 is not exactly a showstopper for me though ;) -- [email protected] mailing list
