freeipa/install
Christian Heimes a8376a2447 Add main guards to a couple of Python scripts
Signed-off-by: Christian Heimes <cheimes@redhat.com>
Reviewed-By: Martin Basti <mbasti@redhat.com>
2016-11-24 16:35:43 +01:00
..
certmonger Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
conf Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
html Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
migration Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
oddjob Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
restart_scripts Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
share Add main guards to a couple of Python scripts 2016-11-24 16:35:43 +01:00
tools services: replace admin_conn with api.Backend.ldap2 2016-11-22 16:17:27 +01:00
ui Build: fix file dependencies for make-css.sh 2016-11-16 09:12:07 +01:00
updates Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
wsgi Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
Makefile.am Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

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.