Hi Stefan thanks for the answer.
I was thinking of the problem and I could only see as a solution the introduction of a small database of the installed modules where their state transitions are recorded. I don't know what database format is recommended by Debian Policy in these cases, but a simple ASCII file would work well to handle the state of the modules, even in the improbable case all the modules available have been selected at least once sometime in the history of a system. I remember Debian Apache 1.x kept a module database in the form of a file listing the Load commands for the modules. If that approach was abandoned some good reason existed though.... Can you envision an approach to the problem? -- Massimo On Mon, 22 Nov 2010 22:19:33 +0100, Stefan Fritsch wrote > > True, that's a problem. But I don't see an elegant solution right > now. On remove, you would have to remember if the package was > enabled and on reinstall, you would then need to restore the > original state. > > It would probably make sense to create one script in the apache > package to handle all this, which can then be used by all the module > packages. But I definitely won't have time to implement that in the > forseeable future. > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact [email protected] > Archive: http://lists.debian.org/[email protected] -- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
