freeipa/install
Martin Basti 2427b2c242 Remove ico files from Makefile
Icons were removed in a4be844809 but still
persist in Makefile. This patch fixes Makefile.

https://fedorahosted.org/freeipa/ticket/823

Reviewed-By: Martin Babinsky <mbabinsk@redhat.com>
2015-07-27 16:19:49 +02:00
..
certmonger plugable: Pass API to plugins on initialization rather than using set_api 2015-07-01 13:05:30 +00:00
conf Provide Kerberos over HTTP (MS-KKDCP) 2015-06-24 10:43:58 +02:00
ffextension webui: append network.negotiate-auth.trusted-uris 2014-09-11 09:41:51 +02:00
html webui: add Kerberos configuration instructions for Chrome 2015-07-27 13:50:49 +02:00
migration migration: Use api.env variables. 2015-07-17 10:30:42 +02:00
oddjob oddjob: avoid chown keytab to sssd if sssd user does not exist 2015-07-16 13:41:08 +02:00
po l10n: Update translation strings 2015-07-07 12:07:15 +02:00
restart_scripts plugable: Pass API to plugins on initialization rather than using set_api 2015-07-01 13:05:30 +00:00
share DNS: Consolidate DNS RR types in API and schema 2015-07-21 17:18:29 +02:00
tools Allow value 'no' for replica-certify-all attr in abort-clean-ruv subcommand 2015-07-17 16:47:18 +02:00
ui Remove ico files from Makefile 2015-07-27 16:19:49 +02:00
updates DNS: Consolidate DNS RR types in API and schema 2015-07-21 17:18:29 +02:00
wsgi Remove trivial path constants from modules 2014-11-04 12:57:01 +01:00
configure.ac trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +02:00
Makefile.am trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +02: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.