freeipa/install
John Dennis 2bc657acab ticket 1660 - update LINGUAS file, add missing po files
Our LINGUAS file and the set of po files have diverged from what's on
Transifex. We should update the LINGUAS file to match the set of
translations on Transifex and add po files currently on Transifex but
not in our git repo to our git repo.
2011-08-18 13:20:06 +02:00
..
conf rename static to ui 2011-01-20 14:12:47 +00:00
html Fixed browser configuration pages 2011-08-17 17:28:25 +00:00
migration Fixed broken links in ipa_error.css and ipa_migration.css. 2011-08-11 13:38:36 +00:00
po ticket 1660 - update LINGUAS file, add missing po files 2011-08-18 13:20:06 +02:00
share Fixed browser configuration pages 2011-08-17 17:28:25 +00:00
tools Ask for reverse DNS zone information in attended install right after asking for DNS forwarders, so that DNS configuration is done in one place. 2011-08-09 13:12:19 +02:00
ui Fixed problem selecting value from combobox 2011-08-17 18:03:29 +00: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.