freeipa/install
Endi S. Dewata 4ff959f55d Removed custom layouts using HTML templates.
The code for supporting custom layouts using HTML templates has been
removed. If it's needed again in the future the code can be restored.

Ticket #1501
2011-07-21 11:47:57 -04:00
..
conf rename static to ui 2011-01-20 14:12:47 +00:00
html HBAC deny warning 2011-07-06 21:52:00 +00:00
migration Removed FreeWay font files. 2011-06-20 12:59:05 -04:00
po Make dogtag an optional (and default un-) installed component in a replica. 2011-06-23 19:04:33 -04:00
share Set the ipa-modrdn plugin precedence to 60 so it runs last 2011-07-17 22:24:30 -04:00
tools Don't delete NIS netgroup compat suffix on 'ipa-nis-manage disable'. 2011-07-19 13:45:01 +02:00
ui Removed custom layouts using HTML templates. 2011-07-21 11:47:57 -04:00
updates Correct sudo runasuser and runasgroup attributes in schema 2011-07-19 08:06:41 -04:00
configure.ac Removed custom layouts using HTML templates. 2011-07-21 11:47:57 -04: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.