Full automatic package install/upgrade/uninstall support
As it came out of DBF07, we need an automatized way to cope with packages installation, upgrading, uninstallation.The goals are
- simplify our package rules
- make the system behaviour more predictable during RPMs transactions
- write less code and in package spec file and update actions,
...and get rid of
nethserver-mail-postmap-update action: expand postfix/postmap template to obtain the list of databases to expand. Refs #1870
postfix/postmap template: add required databases for nethserver-mail-postmap-update action. Refs #1870
/etc/amavisd.conf template: default content inspection type is "amavisd-after-queue" with all checks disabled. Refs #1870
/etc/postfix/master.cf template: default content inspection type is "amavisd-after-queue", connection limits are set only for type "amavisd-before-queue". Refs #1870
/postfix/master.cf template: moved 30amavisd-before-queue fragment to nethserver-mail-filter. Refs #1870
/etc/postfix/master.cf template: Override the default content inspection type. Refs #1870
nethserver-mail-postmap-update action: filter out db file if source does not exist. Refs #1870
nethserver-mail-postmap-update action: warn if source db file does not exist. Refs #1870
nethserver-samba-group-sync action: check if samba idmap backend is functional before going on, and don't fail if a unix group does not exist. Refs #1870
nethserver.py (posttrans_hook): ensure package list is sorted respecting RPM dependencies. Refs #1870
#4 Updated by Davide Principi over 6 years ago
- Status changed from MODIFIED to ON_DEV
- % Done changed from 100 to 30
We must ensure an action is not executed until the owning package is properly configured.
Say a package is configured after its
*-update event has been run.
Currently, if an event comprises actions from different packages it can be signalled before all the bound packages are configured. This happens on new installations, where a lot of packages are installed within the same yum transaction.
For now, the order of
*-update events respects the RPMs dependencies, but if an
-update event starts a sub-event (i.e.
group-create) it happens to execute actions from not-configured packages. Those actions may fail!