After a bit of pondering, filed
https://github.com/rpm-software-management/rpm/issues/3014 instead, we'll
revisit the aliases with this is fixed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/3008#discussioncomment-8995444
You
Could you fix it for your rpmspec aliases though?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/3008#discussioncomment-8982821
You are receiving this because you are subscribed to this thread.
Message ID:
BTW it's worth noting that both the patches and sources appear in a reverse
order to how they're introduced in the spec. This is basically an internal
implementation detail (linked list operation) leaking into the packages, but
because it's always been that way, "fixing" would silently break
The query is not exactly obvious though, so:
https://github.com/rpm-software-management/rpm/pull/3011
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/3008#discussioncomment-8980798
You are receiving this because you are subscribed
> I'd like to be able to query a spec file for the list of its patches.
`rpmspec --srpm -q --qf "[%{PATCH}\n]" `
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/3008#discussioncomment-8980564
You are receiving this because you
This would be tremendously useful, especially for me trying to dig through
really complex packages... Some of them are just not able to be intuited by
reading, and being able to probe them like this would be really useful!
--
Reply to this email directly or view it on GitHub: