David Coutadeur wrote: > > Hello, > > > I have noticed a few changes in the cn=config configuration between openldap > 2.5.1 and 2.5.7. > > The main things that have changed: > > - many modifications in the configuration schema (cn=schema,cn=config) > > - some modifications in the additional schemas (core, cosine,...) > > - a few modifications in the database and overlay entries (for example, > olcDbMaxEntrySize, olcPPolicyDisableWrite, objectClass: olcMemberOf -> > objectClass: > olcMemberOfConfig) > > > It means that, when upgrading OpenLDAP, the previous configuration may not be > compatible with the new OpenLDAP version. > False. Additions to the schema are always forward-compatible. Where we have renamed objectclasses, we have kept the old name as an alias. So old configs will continue to work. > > Considering this, I have 2 questions: > > 1/ Do you plan to continue having evolutions of the configuration schema?
Whenever the need arises. > > 2/ If so, will the previous 2.5 configuration be compatible in the future? We will never break compatibility unless it is totally unavoidable. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
