[Rpm-maint] [PATCH] Mark build-id and dwz entries in packages as %artifact files

Panu Matilainen pmatilai at redhat.com
Wed Nov 8 11:44:03 UTC 2017


On 11/08/2017 12:29 PM, Thierry Vignaud wrote:
> On 8 November 2017 at 10:27, Panu Matilainen <pmatilai at redhat.com> wrote:
>> In worst-case scenarios (packages with lots of binaries but little
>> else), the build-id entries can dominate the query output to the
>> point its hard to see the actual content. Marking these things as
>> %artifact entries (artificial by-products of our processing) allows
>> them to be easily filtered out from queries, eg:
>>
>>    $ rpm -qpl can-utils-20170830git-1.fc27.x86_64.rpm | wc -l
>>    76
>>    $ rpm -qpl --noartifact /can-utils-20170830git-1.fc27.x86_64.rpm | wc -l
>>    28
> 
> I would not list them by default (aka --noartifact would be the default)

Yes, but that's another topic. The problem is rpm doesn't really have 
facilities for handling the no-case being default.

>> Besides build-ids in the main package(s), this also marks the build-id
>> and dwz-related entries in the debuginfo packages as %artifacts. The
>> debuginfo files exist solely for carrying debuginfo data so its arguable
>> whether these should be %artifacts in there too or only in the main
>> packages, comments welcome...
> 
> I would say the should not be tagged as such

That was my first instinct as well, but then again one could argue that 
the actual content of debuginfo packages is the 
/usr/lib/debug/[...]/*.debug files and the build-ids are just as 
artificial by-products here as they are in the main packages.

	- Panu -


More information about the Rpm-maint mailing list