freeipa/install
Stanislav Levin 09750589f5 Drop concatenated title of remove dialog
As for now the default title of remove dialogs is set to
'Remove ${entity}', where 'entity' is also translatable text.
This construction is used via method 'create_remove_dialog'
of Search facet for the all association 'Delete' actions of
entities.

The such concatenation leads to a bad quality translation and
should be changed to an entire sentence.

From now a mentioned title is taken from a spec and should be
specified explicitly.

Fixes: https://pagure.io/freeipa/issue/7699
Reviewed-By: Serhii Tsymbaliuk <stsymbal@redhat.com>
2018-09-18 13:51:51 +02:00
..
certmonger Generate scripts from templates 2018-08-23 14:49:06 +02:00
html Fix translation of "ssbrowser.html" Web page 2018-09-12 10:44:37 +02:00
migration Clean up migration "error" and "invalid" pages from project 2018-08-27 17:10:32 +02:00
oddjob Generate scripts from templates 2018-08-23 14:49:06 +02:00
restart_scripts Generate scripts from templates 2018-08-23 14:49:06 +02:00
share Disable authentication to endpoint for serving i18n requests 2018-07-17 15:32:28 -04:00
tools Remove DL0 specific code from ipa-ca-install 2018-09-12 13:11:21 +02:00
ui Drop concatenated title of remove dialog 2018-09-18 13:51:51 +02:00
updates Use replace instead of add to set new default ipaSELinuxUserMapOrder 2018-06-08 10:49:18 +02:00
wsgi Add absolute_import future imports 2018-04-20 09:43:37 +02:00
Makefile.am Encrypt httpd key stored on disk 2018-03-23 12:48:46 +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.