freeipa/install
Timo Aaltonen 358acdd85f Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
..
certmonger Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
custodia Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
html Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
migration Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
oddjob Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
restart_scripts Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
share Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
tools Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
ui Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
updates Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
wsgi Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
Makefile.am Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
Makefile.in Imported Debian patch 4.8.10-2 2021-10-03 12:58:58 +02:00
README.schema Imported Upstream version 4.6.2 2021-07-25 07:32:41 +02:00

README.schema

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.