
Am 16.12.20 um 10:50 schrieb Dan Čermák:
Olaf Hering <olaf@aepfle.de> writes:
Am Wed, 16 Dec 2020 10:08:43 +0100 schrieb Dan Čermák <dcermak@suse.com>:
transaction file triggers This other idea is about moving the "restart" around, which is unrelated to what needs to be fixed for SUSE: we need to remove files below /etc from packages, which requires to preserve modified files that where marked as %config. A brief search gave no hints about the ordering of these "triggers".
If I understand https://github.com/rpm-software-management/rpm/blob/5ce2b5e3121aa07eb1ccf2bc... correctly, then first %transfiletriggerun are run, then %posttrans, then %transfiletriggerpostun and at last %transfiletriggerin.
I am not sure how exactly the %posttrans scriptlets are ordered, but my guess from https://github.com/rpm-software-management/rpm/blob/5ce2b5e3121aa07eb1ccf2bc... is that they are run in the same order that the packages are installed/upgraded.
This all of course only applies if you use rpm/librpm to run these scriptlets, which afaik is not done by zypper. Maybe Michael and/or Benjamin can shed some light here? Currently the transfiletrigger are not executed by zypper because we are installing each rpm package separately collecting the posttrans scripts by using a feature that disables them and instead prints which scripts would have been run. RPM has not yet a feature to detect the transfiletriggers that would've been executed, sadly the previously mentioned feature disables the them completely.
Cheers,
Dan
-- Benjamin Zeller <bzeller@suse.de> Systems Programmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuremberg, Germany Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer