On Tue, May 10, 2005 at 12:48:01PM +0200, Tore Anderson wrote: > * Uwe Steinmann > > > 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". That answers the 2nd/3rd question, whether a module should be deactivated (if I get you right). > A user must be allowed to have full control over the configuration of > a package without fearing "pleasant" suprises such as modules getting > enabled/disabled without him knowing. Does that mean that, 'yes' a webapp must enable all apache modules it needs, but it should ask the the user first? Uwe -- MMK GmbH, Universitaetsstr. 11, 58097 Hagen Uwe.Steinmann@mmk-hagen.de Tel: +2331 840446 Fax: +2331 843920
Attachment:
signature.asc
Description: Digital signature