Bug#228791: apache: modules-config name and/or location too general
severity 228791 wishlist
tags 228781 wontfix
stop
quit
Hi Jeroen,
On Tue, 20 Jan 2004, Jeroen van Wolffelaar wrote:
> Since shortishly, apache uses /usr/sbin/modules-config for providing an
> interface to update the available and loaded modules in apache.
>
> First, the name seems a bit general to me: it has not the word 'apache'
> in it, and it is in no way at first sight clear that this is an
> apache-specific script (except when you look at source and manpage of
> course...).
The reason why there is no "apache" word in it is that we ship 3 flavours
of apache. After a big cleanup of name clashing around the 3 flavours
(apache, apache-ssl and apache-perl) if we have to ship an
apache-modules-whatvername than people would expect also the other 3 and
that won't be the case. Plus expandig modules-config in the future to
support for instance apache2 or other webservers is relatively simple.
>
> Second, I might be wrong about this, but I do not believe that there is
> an imminent reason to have this script in /usr/sbin. I think this script
> belongs better in /usr/share/apache-common/(bin/)modules-config or
> something like that. If done this way, the general name is not a problem
> anymore, since it isn't in global program namespace anymore.
No becuase modules-config is a tool that can be used anytime by the
administrator. /usr/sbin is the proper localtion.
Fabio
--
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues
http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp00004.html
Reply to: