Quanah, I think I've pissed you off. I apologise. Well, if you don't see
the problem, then that's fine. No need to get pissed off. You don't have
to reply. That's fine. Just chill, man. It's not good for you. I read
the whole admin guide and man pages. I'm not complaining just because
out of ignorance. That kind of assumption is just a personal attack, not
very nice of you(thf, I started it. Sorry). I'm making this point
because I care about OpenLDAP and I want it to be better. I don't
understand why we have to get emotional here.
I know how to import schemas with cn=config. That was never a question.
I was just complaining because it's a tedious process and I believe that
it shouldn't be like this. The whole cn=config matter was not even my
question in the first place. My concern was that I'm not happy with how
cn=config handles schemas and I want to stick with "deprecated"
slapd.conf. slaptest has to be used to convert schema to ldif, which is
in no way intuitive and convenient.
On 5/4/22 12:27, Quanah Gibson-Mount wrote:
And you're literally missing the point that a ".schema" file is a
syntax specific to slapd.conf and a ".ldif" file is a syntax specific
to cn=config. Just as you cannot load a ".schema" file into
cn=config, you cannot load a ".ldif" file into slapd.conf. The two
things are *equivalent* representations for their respective
configuration types. In the future, expect only ".ldif" files to get
shipped once we finalize deprecating slapd.conf.
The format of schema is defined in RFC 4512. It's universal. OpenLDAP
has no right to be difficult in incorporating schemas. Forcing users to
convert it to ldif to just fit into the OpenLDAP specific cn=config
format is not just fair, especially for the sake of compatibility. I'd
have been happy if I could just use include: attribute to load .schema.
To anyone else, just forget everything I said. I just wanted to know
when the slapd.conf support will be dropped. THAT was my question.
And, don't get me wrong. cn=config is a great idea!
