Please use depend.apache.eclass to depend on apache, and please install a sane default config in /etc/apache2/modules.d/
Please development your argument at bit, I currently see no point in using this eclass.
ebuild depending on apache must use depend.apache.eclass to make it maintainable for future changes. when installing an apache module (which this ebuild appearantly does) you must install a configuration snippet to load the module and provide a default config if applicable.
erf, my reply didn't make it it seems. This package doesn't install a module and it's configuration is interpreted by variables that only the user owned process knows about. Is there some other reason we should use the eclass for ?
i didn't install it because of depdency hell, but why does configure use the apache module dir? i would still prefer if you just call need_apache2 like every other ebuild. if you don't feel like it, just close the bug then
(In reply to comment #4) > i didn't install it because of depdency hell, but why does configure use the > apache module dir? it is needed to known where modules are so that the custom configuration file can load them. > i would still prefer if you just call need_apache2 like every other ebuild. if > you don't feel like it, just close the bug then I'll add this. However it will not spare me the need to add the dependency by hand to check for apache USE flags. Is there a nice way to solve this use case ?
(In reply to comment #5) > I'll add this. However it will not spare me the need to add the dependency by > hand to check for apache USE flags. Is there a nice way to solve this use case > ? the eclass has been written before USE deps were supported. just leave it as-is for now, maybe i will convert the eclass to EAPI 2+ some day
