I wonder if we can just have some extension tags to easier access the parts of
`sourcerpm` that do the parsing for you. That would also work for old packages
(if only with the new rpm binary)
--
Reply to this email directly or view it on GitHub:
Sorry, I don't understand that question. Parsing NEVR is not a whole lot
different or better from parsing SOURCERPM, because the latter is literally
just NVR.[no]src.rpm (since epoch isn't there, it's actually easier to parse
than NEVR). What would (IMO) make an actual difference is having
Is NEVR format saved in headers? If it was, it could be used when parsing NEVR.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
SOURCEPACKAGE is used for identifying *source packages*, ie it's set to 1 on
src.rpm headers.
If we added SOURCENAME, the next person would want SOURCEVERSION, -RELEASE and
-EPOCH, (because they can differ from the binary package counterparts) and so
on. The idea is that SOURCERPM tells you
There is SOURCEPACKAGE, but it is not used:
```
[root@rosa-2019 metacity]# rpm -q --querytags bash | grep SOURCE
NOSOURCE
SOURCE
SOURCEPACKAGE
SOURCEPKGID
SOURCERPM
[root@rosa-2019 metacity]# rpm -q --qf '%{SOURCEPACKAGE}\n' bash
(none)
```
--
You are receiving this because you are subscribed
I am a bit fed up with RPM's inability to show the value of "Name:" tag of the
spec from which the package was built. `rpm -q --qf '%{sourcerpm}\n` shows
something like `metacity-3.34.1-1.src.rpm` and I have to use strange
combinations of comsnds to extract the real name "metacity" from this.
