MIkey wrote: > A server profile should be as basic as possible. Choices like which apache > version, which version of php, which mta, etc... should be left up to the > person building the server, as opposed to what some particular gentoo > developers favorite version of X is. > > I would also like, some day, to be able to use catalyst to build server > install images without having to hack profiles. It seems to me the proper > place to use the apache2 flag would be either in make.conf or > package.use... Just a thought. >
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 example as it's build environment is more complex but my point is the same). Leaving apache2 off while having a stable apache-2.0 in the tree will and does lead to confusion, because when an add-on module is installed with the apache2 USE-flag disabled, apache-1.3 will be installed - not usually what the user wants. It's not the developers choosing which line of apache is default, it's a portage thing - portage always prefers the highest version of a package. Thus the apache2 USE flag needs to stay enabled. If we choose to remove apache2 from the default USE-flags, then the profile needs to mask >=apache-2.0 as well. -- 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
