Expanding RPM macros

Sun Nov 2 20:19:29 UTC 2014

It is possible to embed a macro value in the binary, not the other way 
(Actually you could use lua to read the version string from a source 
file but it is more fragile).


W dniu 02.11.2014 o 20:33, Peter Lemenkov pisze:
> Hello All!
> One of my packages defines an essential information regarding the API
> (API version string) during the %build stage. It's possible to extract
> this information by invoking a binary from the %{buildroot} with
> certain parameters. I'd love to add this information to the spec-file
> during to Provides. Something like
> Provides: %{name}_api_ver = %(%{buildroot}/bin/app --some params)
> Unfortunately it seems that rpmbuild tries to expand all macros at the
> very initial stage when this binary isn't available yet (not built
> yet). I've tied playing with %{eval: ...} but without any luck.
> Could anyone tell me if it's possible at all? And if possible how
> could this be achieved?
> Also I wonder why even rpmbuild -bs performs macro expansion? I
> thought it should just pack spec-file and sources/patches together.

More information about the Rpm-list mailing list