<p></p>
<blockquote>
<p>They're not incompatible with each other, but for the purpose of addressing the issue that libraries should not have to be packaged as executable, <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="719208532" data-permission-text="Title is private" data-url="https://github.com/rpm-software-management/rpm/issues/1394" data-hovercard-type="pull_request" data-hovercard-url="/rpm-software-management/rpm/pull/1394/hovercard" href="https://github.com/rpm-software-management/rpm/pull/1394">#1394</a> kills the ability to chmod a-x to disable dependency generation for all ELF files, whereas <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="719250684" data-permission-text="Title is private" data-url="https://github.com/rpm-software-management/rpm/issues/1395" data-hovercard-type="pull_request" data-hovercard-url="/rpm-software-management/rpm/pull/1395/hovercard" href="https://github.com/rpm-software-management/rpm/pull/1395">#1395</a> doesn't.</p>
</blockquote>
<p>Maybe my understanding of the history is wrong, but I thought the reason we had the <code>chmod a-x</code> hack in the first place was that we didn't have <em>any</em> other way to filter dependencies. Now we have the ability to apply autodep filters based on file names/paths independent of a specific generator, so this hack is no longer needed in the first place.</p>
<blockquote>
<p>But then the latter requires libraries to be executable in the first place, which is a bit silly but that's how at least autotools installs them. Dunno about newer build-tool chains.</p>
</blockquote>
<p>While Autotools, CMake, and Meson all do set libraries to be executable by default, many other toolchains do not. Especially a lot of the custom "portable" ones that come from a Windows-centric don't, since marking a DLL as executable does nothing since DLLs differ from executables by missing the marker in the file that indicates it can be executed rather than requiring an "interpreter".</p>
<blockquote>
<p>Maybe the real "issue" behind this all is that perhaps it's time to admit that the executable bit as a marker for dependency generation has long since stopped being meaningful. And if it's not meaningful for one thing then should it be meaningful for anything at all then?</p>
</blockquote>
<p>Perhaps. We have a richer ways of doing things these days, but I can't say for certain if nobody relies on the <code>exeonly</code> thing for other stuff.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you commented.<br />Reply to this email directly, <a href="https://github.com/rpm-software-management/rpm/pull/1393#issuecomment-732223556">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ADLPZU7AXL27HJUD6DKBEYLSRJ3ZPANCNFSM4SLI2EGA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/ADLPZU35MA3ANX2KMLUSC33SRJ3ZPA5CNFSM4SLI2EGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFOSNQRA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/rpm-software-management/rpm/pull/1393#issuecomment-732223556",
"url": "https://github.com/rpm-software-management/rpm/pull/1393#issuecomment-732223556",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>