<blockquote>
<p>Note that eu-elfcompress does the same. Not that it really should matter which tool does it.<br>
Currently find-debuginfo.sh uses tools from both binutils and elfutils, it might be nice to only<br>
depend on one set of tools (my preference would obviously be to migrate everything to the<br>
elfutils toolset).</p>
</blockquote>
<p>I have no preference at this point. AFAIU both tools use the same zlib library to do the compression, so there's no benefit from choosing on or the other.</p>
<blockquote>
<p>There is also zlib-gnu, the older, pre-standard, compression. Dunno if we want to support that<br>
too.</p>
</blockquote>
<p>I don't see that as useful now, but it's easy to add later if someone want this.</p>
<blockquote>
<p>I do think that this is a nice option to have in theory. But I haven't tried it myself yet</p>
</blockquote>
<p>OK, good to hear.</p>
<blockquote>
<blockquote>
<p><a href="https://github.com/rpm-software-management/rpm/pull/795.patch">https://github.com/rpm-software-management/rpm/pull/795.patch</a> <a href="https://github.com/rpm-software-management/rpm/pull/795.diff">https://github.com/rpm-software-management/rpm/pull/795.diff</a></p>
<ul>
<li>id="<code>readelf -Wn "${RPM_BUILD_ROOT}/usr/lib/debug/.dwz/${dwz_multifile_name}" \ - 2>/dev/null | sed -n 's/^ Build ID: \([0-9a-f]\+\)/\1/p'</code>"<br>
I am slightly surprised we don't seem to use the dwz build-id. Could you double check<br>
we don't actually need that id?</li>
</ul>
</blockquote>
</blockquote>
<p>AFAIU, yes, we don't need it. I've split this part off into a separate pull request: <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="485147208" data-permission-text="Issue title is private" data-url="https://github.com/rpm-software-management/rpm/issues/825" data-hovercard-type="pull_request" data-hovercard-url="/rpm-software-management/rpm/pull/825/hovercard" href="https://github.com/rpm-software-management/rpm/pull/825">#825</a>.</p>
<blockquote>
<p>Also, is there really no distro that is contemplating to use this?<br>
If not, then maybe it is better to not add the extra complexity till someone really wants it</p>
</blockquote>
<p>Well, my intention is to propose this as patch for the rpm package in openSUSE Tumbleweed, either as upstream backport, or as local patch. Obviously I'd prefer a backport ;) .</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/795?email_source=notifications&email_token=ADLPZU7NHQESXDUMOOJNF7TQGO4L3A5CNFSM4IE2KBNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5ECSRA#issuecomment-524822852">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ADLPZU4ARJKKD3JY54MLLE3QGO4L3ANCNFSM4IE2KBNA">mute the thread</a>.<img src="https://github.com/notifications/beacon/ADLPZU7OIM74AAU5UFLYJHTQGO4L3A5CNFSM4IE2KBNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5ECSRA.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/795?email_source=notifications\u0026email_token=ADLPZU7NHQESXDUMOOJNF7TQGO4L3A5CNFSM4IE2KBNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5ECSRA#issuecomment-524822852",
"url": "https://github.com/rpm-software-management/rpm/pull/795?email_source=notifications\u0026email_token=ADLPZU7NHQESXDUMOOJNF7TQGO4L3A5CNFSM4IE2KBNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5ECSRA#issuecomment-524822852",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>