Haven't read this all, but it seems to fit the bill wrt. use case
I tried to tackle at the mock side in the past:
https://github.com/rpm-software-management/mock/issues/11
Nice to see it's becoming a popular request, finally :-)
--
You are receiving this because you are subscribed to this
Like in `-debuginfo`, where it might further help in case of unannounced
ABI breaks?
I see the value of this also for other things, e.g., witnessed daisy
chained breakages because of particular subtle change in linker's
behaviour, thought this is covered with annotations in ELF notes
these days,
Conan-Kudo approved this pull request.
LGTM
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> Isn't that what the `--quiet` switch is for...?
No, definitely no. Because --quiet switch suppresses all output, so the output
of rpm -ql of a normal package with a set of files included in will be also
empty.
Example:
$ rpm -ql bzip2-devel-1.0.6-28.fc29.x86_64 | wc -l
6
$ rpm -ql --quiet
Isn't that what the `--quiet` switch is for...? I'm not sure this patch makes
sense...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
This notice makes a problem when you want to process an output of rpm -ql of an
empty rpm package in a shell script.
Example:
$ rpm -ql gpg-pubkey-f2ee9d55-560cfc0a
(contains no files)
$ rpm -ql gpg-pubkey-f2ee9d55-560cfc0a | wc -l
1
---
But the package is empty!
You can view, comment on, or
