freeipa/install
2011-01-25 14:01:36 -05:00
..
conf rename static to ui 2011-01-20 14:12:47 +00:00
html type prevented rendering on firefox4 2010-12-17 16:07:09 -05:00
migration Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
po Removed 'name' from 'Sudo Command Group name'. 2011-01-24 13:33:00 -05:00
share Enforce uniqueness on (key,info) pairs in automount keys 2011-01-25 11:13:10 -05:00
tools Fix assorted bugs found by pylint 2011-01-25 14:01:36 -05:00
ui action panel select for multiple entities 2011-01-25 13:54:57 -05:00
updates Move automount, default HBAC services, netgroup and hostgroup bootstrapping. 2010-12-17 17:31:19 -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.