On Sunday 08 June 2003 21:45, Robin H.Johnson wrote: > 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. This is what the apache2 use variable is supposed to do. At least, as far as I know. > > 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. I agree with both points. Paul -- Paul de Vrieze Researcher Mail: pauldv@cs.kun.nl Homepage: http://www.devrieze.net