[Rpm-maint] [rpm-software-management/rpm] RFE: make %{load: } work in %prep (#571)
nim-nim
notifications at github.com
Fri Oct 19 09:34:30 UTC 2018
Thanks a lot Panu, it like it a lot better than the shell script option!
Unfortunately I've just seen another similar package wants to use the info in the shipped macros to `ExclusiveArch` itself so that rules out using a `%prep` method.
I may end up replacing all this by sed-ing things in macro files from spec definitions, like fedora-release does, which kind of sucks since the result is not too readable and puts the master definition in the spec file not the scm-managed macro project.
Though I guess it should be possible to write a macro that automates such kind of sed-ing. fedora-release could use it. As does fontpackages. As does go-macros. And there are probably others I have no knowledge of.
@pmatilai do you think a macro
* that takes as first argument a rpm constant or function defined in the spec,
* that takes as second argument a macro filename available somewhere in _builddir during %prep
* and puts the spec definition of the rpm constant or function in the macro file
* eventually replacing exisiting defs in this file
Is doable?
The main problem I see it things that take multiline definitions (esp if you need to replace an existing def). Is there a way to scope those easily in rpm ?
Alternatively, one could force the use of a @@foo@@ anchor in the target macro file, by changing "put spec def as-is in the target macro file" with "replace the anchor with the def of xxxx in zzz macro file"
What do you think ?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/571#issuecomment-431304832
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20181019/2414ddda/attachment.html>
More information about the Rpm-maint
mailing list