mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2024-12-26 08:51:50 -06:00
6a8eeff22d
To update install/ui/css/patternfly.css you should: 1. clone Bootstrap 3, Font-Awesome, Bootstrap-Select and PatternFly to the same parent directory as for FreeIPA (or use symlinks) 2. checkout desired versions of each component 3. run install/ui/util/make-patternfly.css 4. when changing component versions, copy xxx/variables.less from each component to install/ui/less/xxx/ so we can use the variables in our less files This commit contain css made from component versions as follows: - PatternFly: 0.2.5 - Bootstrap: 3.1.1 - Bootstrap-select: 1.4.3 - Font-Awesome: 4.0.3 Reviewed-By: Endi Sukma Dewata <edewata@redhat.com> |
||
|---|---|---|
| .. | ||
| certmonger | ||
| conf | ||
| ffextension | ||
| html | ||
| migration | ||
| po | ||
| restart_scripts | ||
| share | ||
| tools | ||
| ui | ||
| updates | ||
| wsgi | ||
| configure.ac | ||
| Makefile.am | ||
| README.schema | ||
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.