Re: support for rfc2307bis

[Mark Reynolds <mareynol@xxxxxxxxxx>]

On 10/18/2017 02:18 PM, Winstanley, Anthony wrote:

After reading Trevor's thread on schema, there's a core issue here:

 

How does one go about choosing between RFC2307 and RFC2307bis? (They are incompatible: You can't have both.)

Is it RedHat's position to mandate the use of RFC2307 and remove RFC2307bis as a supported option?

 

(In other words, if you want RFC2307bis, you're on your own, and you'll have to deal with the possibility that any changes you make to core schema might be subsequently undone by updates to 389-ds.)

Correct as of today 10rfc2307.ldif is part of the standard system schema, and if you remove that file, it will get added back during an upgrade.

We do ship the alternate version here (as well as other alternative schema):   /usr/share/dirsrv/data/10rfc2307bis.ldif

The issue here is that since we've always shipped rfc2307 we can not just swap it out with a version that could break existing clients/applications.   And rfc2307bis was never published by the IETF as an RFC.  There is nothing stopping you from using rfc2307bis, you just need to remember to replace it after an upgrade.

You can also file an RFE (https://pagure.io/389-ds-base/new_issue) to add a feature to the installer where you can specify schema changes like this.  One could even argue it should be in the standard schema, but a change that like could not happen until the next major version (aka 389-ds-base-1.4.0)

Regards,
Mark

 

Anthony

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx