freeipa/install
2011-02-21 15:36:37 -05:00
..
conf rename static to ui 2011-01-20 14:12:47 +00:00
html error handling style 2011-01-25 16:47:09 -05:00
migration Fix migration page 2011-02-11 13:28:22 -05:00
po Update Polish & Ukrainian translations 2011-02-18 10:30:32 -05:00
share Browser configuration support for Firefox 4 2011-02-17 12:12:23 -05:00
tools Fixed in ipa-server-install help and man page 2011-02-18 10:00:48 -05:00
ui Updated test data files. 2011-02-21 15:36:37 -05:00
updates Add aci to make managed netgroups immutable. 2011-02-18 15:29:51 -05:00
configure.ac rename static to ui 2011-01-20 14:12:47 +00:00
Makefile.am rename static to ui 2011-01-20 14:12:47 +00: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.