freeipa/install
2011-03-03 15:38:53 -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 Final i18n unit test fixes. 2011-03-01 10:31:43 -05:00
share Store list of non-master replicas in DIT and provide way to list them 2011-03-02 09:46:46 -05:00
tools IPA replica/server install does not check for a client 2011-03-03 10:20:39 -05:00
ui fix truncated message 2011-03-03 15:38:53 -05:00
updates Store list of non-master replicas in DIT and provide way to list them 2011-03-02 09:46:46 -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.