Make it possible to evaluate arbitrary macros in the context of a given spec file #3008
Replies: 4 comments 2 replies
-
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! |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
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 anybody counting on the current behavior :-/ |
Beta Was this translation helpful? Give feedback.
-
After a bit of pondering, filed #3014 instead, we'll revisit the aliases with this is fixed. |
Beta Was this translation helpful? Give feedback.
-
Particular use case: I'd like to be able to query a spec file for the list of its patches. Currently (on Fedora 39's 4.19.1) this is only possible using
rpmspec --shell
but it requires parsing the output:without shell,
rpmspec
only allows querying query tags e.g.While
rpm
allows evaluating anything but only those define by shipped macros, not definitions that are spec file specific;rpmspec
does seem to have a-E
eval option but it is undocumented and does not seem to workBeta Was this translation helpful? Give feedback.
All reactions