freeipa/install
Petr Spacek c0674e89d1 Build: fix make clean for web UI
https://fedorahosted.org/freeipa/ticket/6418

Reviewed-By: Martin Basti <mbasti@redhat.com>
Reviewed-By: Christian Heimes <cheimes@redhat.com>
2016-11-09 13:08:32 +01:00
..
certmonger install: remove dirman_pw from services 2016-11-07 11:34:03 +01:00
conf Use Dogtag REST API for certificate requests 2016-09-07 12:49:28 +02:00
html Added warning to user for Internet Explorer 2016-04-28 14:28:11 +02:00
migration ipaldap: merge IPAdmin to LDAPClient 2016-11-07 11:34:03 +01:00
oddjob Build: fix distribution of oddjob files 2016-11-09 13:08:32 +01:00
restart_scripts install: remove dirman_pw from services 2016-11-07 11:34:03 +01:00
share Build: fix KDC proxy installation and remove unused kdcproxy.conf 2016-11-09 13:08:32 +01:00
tools Build: do not compress manual pages at install time 2016-11-09 13:08:32 +01:00
ui Build: fix make clean for web UI 2016-11-09 13:08:32 +01:00
updates Build: fix distribution and installation of update LDIFs 2016-11-09 13:08:32 +01:00
wsgi Modernize 'except' clauses 2015-08-12 18:17:23 +02:00
Makefile.am Build: fix distribution of install/REDME.schema file 2016-11-09 13:08:32 +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.