On 11/7/19 5:24 PM, Peter Lemenkov wrote:
Hello All,
We have a set of macros for Erlang libraries rpm building. Some of
these macros evaliated before actual build (if I understand RPM build
process correctly) and their actual value depends on a type of a
package - arch-dependent or noarch.
Previously we've used %{buildarch} macro to distinguish between
noarch-packages and arch-specific and that worked well enough.
Unfortunately this macro was removed recently.
Is there a way to pass "noarch" to some scripts from
/usr/lib/rpms/macros.d when building noarch package? Spec-file was
marked already as BuildArch: noarch. Where this information is stored
now?
%{_target_cpu} should work for the purpose, and actually provide
reliable and accurate data unlike %{buildarch} which can contain
multiple values, or whose values could be maskes by having multiple
BuildArch: lines in the spec etc.
- Pabnu
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
