[Rpm-maint] [rpm-software-management/rpm] Allow packagers to specify individual scriptlets as critical (5455f02)

[Jeff Johnson]

The reasoning for not reverting the original change is badly flawed, both then and now.

Ignoring scriptlet returns because of packaging flaws masks the problem and prevents fixes. If packaging errors (like forgetting || :) are common, then the issue needs to be brought to the packaging committee with a suggested macro to make it harder for a packager to make an error.

Another approach (like ldconfig) is to fully automate, say, info execution in rpm and handle --nodocs correctly.

If you don't wish duplicate headers (because a failed install, including failed scriptlet, disables the matching erase, then unregistered the failed install header when a scriptlet fails. The real problem for a package manager is the file content has changed in unpredictable ways, and that has nothing to do with scriptlet exit codes.

But if you insist on a new feature (like -c on scriptlets), then you need to add a rpmlib tracking dependency to ensure that a package with *critical* scripts has a prayer of being associated with a version of rpm that understands %post -c

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/commit/5455f02523a9b8583d5a942a6d97f1084f3093df#commitcomment-28018124
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20180309/c2f9095b/attachment.html>