Re: Should webapp enable an apache module if needed?
On Tue, May 10, 2005 12:48, Tore Anderson wrote:
>> No I wonder if each package using apache2 is responsible for activating
>> any required module in its postinst script? egroupware (and probably
>> other packackes including one of mine), don't activate mod_php4. Is this
>> considered a bug? What if the package is deinstalled? Should it
>> deactivate the module? I guess not, since others may need it.
>
> A package should never change the configuration of another package,
> at least not without asking a question that defaults to "no".
Indeed, a "Depends" on the specific module (like libapache2-mod-php4)
should be enough to make sure that module is available. The module package
should take care of setting itself up correctly, or not if the user wishes
so (or changes that later).
However, it is of course good for your application to fail gracefully when
a module is not enabled. With the php4 module this is a bit different, but
your webapp could check for mod_rewrite (on run, not on install since the
apache config can also be changed after package installation). If not
enabled, warn the user and provide a hint on what to do.
Thijs
Reply to: