On Sun, Jun 08, 2003 at 06:12:21AM -0400, Ned Ludd wrote: > After writing a net-www/ ebuild it seemed apparent to me that we are > going to need an apache.eclass. A quick find in portage reveals quite a > few independent ebuilds all needing the basic functionality that could > be provided by an apache.eclass I agree that having this would be worthwhile, however it has been said higher up before that /home/httpd/htdocs would be where things were installed. > syntactically perfect the idea is what matters.. > I have attached an apache.eclass that I welcome your input/feedback on. > While it may not be syntactically perfect for the apache2 part its the > idea that we get this out there and start talking about one that > matters. A few problems with this. 1. What about people that have both installed? I actually have an open bug for mod_php about this, and I'm trying to decide on a workable solution. Presently I'm leaning towards an enviroment variable 'FORCE_APACHE=1|2' that overrides any detection routines, for the special case of people that have both. 2. All of the functions start misbehaving when you have multiple instances of the User/Group/DocumentRoot configuration directives. 3. The 'newdepend virtual/glibc sys-apps/gawk sys-apps/grep' is questionable. newdepend is definately correct for the apache install, however the others shouldn't be required at runtime. -- Robin Hugh Johnson E-Mail : robbat2@orbis-terrarum.net Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85