[Rpm-maint] [rpm-software-management/rpm] Why find-debuginfo script only operates on executable files? (Discussion #3195)

[Michal Domonkos]

(Just FYI, @pmatilai is on vacation until August.)

This is a convention (at least on Linux) for shared libraries to be executable. It's also [mandated](https://docs.fedoraproject.org/en-US/packaging-guidelines/Debuginfo/#_checking_your_debuginfo_package_for_usefulness) by Fedora Packaging Guidelines. I'm not familiar with the actual reasoning behind it but a quick google search gives some [clues](https://unix.stackexchange.com/a/61650).

As to why find-debuginfo.sh only looks for those that *are* executable: Looking at the git log, this check apparently has been in place since the very first version of the script added in 2002 (commit 90b34cd4e51de9b69a1a1e4bf58fcee31c2bf192). That said, the brp-strip-shared script, on the other hand, does *not* have this filter (and instead mentions in a cryptic comment that "our libraries aren't +x").

In any case, you may want to ask about this at https://sourceware.org/debugedit/ (which is where find-debuginfo.sh is nowadays shipped). I personally don't think anybody would change this now after those 20+ years. Even if the check itself turns out to non-sensical, it should be considered a "feature" at this point because changing it would inevitably break somebody's packages.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/3195#discussioncomment-10018894
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/repo-discussions/3195/comments/10018894 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20240711/205c3848/attachment-0001.html>