On Thu, Jul 15, 2010 at 09:30:16PM +0200, Petter Reinholdtsen wrote:
Since OpenLDAP 2.3, it has been possible to store the LDAP configuration (as in schemas, ACLs etc) in the LDAP database itself, allowing it be changed without restarting the LDAP database.The setup is documented in <URL: http://www.zarafa.com/wiki/index.php/OpenLdap:_Switch_to_dynamic_config_backend_(cn%3Dconfig) >. Should we switch to this kind of setup in Debian Edu too?
Another important "benefit" of moving configuration from filesystem to database (both here and other places like ISC BIND to PowerDNS move) is that database is not governed by Debian Policy as /etc in filesystem is.
This circumvents the infamous bug#311188.I deliberately say "circumvent" (not resolve) and quote "benefit" as really I do not see it as a good approach to deal with ownership issues of file-based configuration by avoiding file-based configuration.
There is a very sane logic in the package maintainer owning the configuration files tied to a package. Only the package maintainer can handle transitions in configuration defaults or perhaps larger changes like change of configuration format.
Bypassing package maintainer configuration means taking over that important task of transitions as well.
Debian Edu aims at being a Debian Pure Blend. So solving bug#311188 is important. But I believe Debian Edu is also interested in being upgradeable (i.e. not requiring fresh install at a major upgrade of Debian), and to achieve that goal - without putting a big burden on custom development - I believe the configuration format used by Debian packaging whould be used, even if the underlying code supports alternatives - for the very reason of keeping closely tied to the Debian maintainance (which is deceivingly easy to *avoid* when seeking ways to solve bug#311188).
Sorry, I do not have an easy solution, only a touch one: For each and every package, the Debian maintainer *must* be convinced to officially support whatever configuration customization Debian Edu needs to apply.
Circumvention of Debian Package Maintainance - even if "compliant" with Debian Policy, is bad for a maintainable Debian Edu.
Hope this makes sense. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Attachment:
signature.asc
Description: Digital signature