As part of some of the work I've done in OpenMandriva in transitioning the RPM
stack from rpm5.org to rpm.org RPM, I've discovered that there was an
_interesting_ behavioral difference with `%exclude`.
In rpm5.org RPM, `%exclude` does not give you a "get out of jail free" card to
bypass the file list check. A file that is marked by `%exclude` in one
subpackage but isn't included in any other subpackage triggers the unpackaged
files error. This does not happen in rpm.org. RPM.
I would argue that the rpm.org behavior is a bug, as there's not a particularly
obvious reason for why it works this way. Moreover, it leads to accidental
packaging bugs.
Can we change this behavior for the upcoming RPM 4.16?
--
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/issues/994
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
