here is a patch that check the usage of rpath by using the already existing rpmlint check.
attachment 0006-use-rpmlint-to-see-if-rpath-is-set-or-not.patch
I wonder if we should follow the same approach as in #40 here.
Fail if we find something, leave empty if we find nothing.
The rpmlint check is IMHO simple enough to be working in all cases, and if rpmlint do not see that a binary is using rpath, that's either chkrpath who is broken ( and so a human would not see it either ), or rpmlint ( and then, FedoraReview should not assume that rpmlint is broken by default ).
rpath is really something that can be automated.
Applied and pushed
Login to comment on this ticket.