Files
freeipa/install
Endi S. Dewata be17fed8c4 Fixed problem unprovisioning service.
The IPA.service_provisioning_status_widget has been modified to
execute the disable command with the right entity name.

Ticket #1543
2011-07-28 21:47:07 +00:00
..
2011-01-20 14:12:47 +00:00
2011-07-06 21:52:00 +00:00
2011-06-20 12:59:05 -04:00
2011-07-26 22:30:21 -04:00
2011-07-28 21:47:07 +00:00
2011-01-20 14:12:47 +00: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.