On 11/17/18 11:35 AM, hyc@symas.com wrote:
We could instead ship an update.ldif containing the mods between different schema versions, that must be applied with slapmodify during the update process...
IMO too many prerequisites must be perfectly full-filled and thus is too fragile.
That's one of the things where e.g. OpenDS/OpenDJ does a much better job with its cn=config: The schema shipped with the server is stored in various LDIF files in a config directory along with file rootdse.ldif holding cn=config. Schema directly added by modifying cn=schema is sent to a separate user schema file.
With such a layout the standard schema shipped with the software is not part of cn=config but can still be dynamically changed (by directly modifying subschema subentry). But there's always a way out of trouble because you can manually fix the separate LDIF schema file(s).
Ciao, Michael.