[Rpm-maint] [rpm-software-management/rpm] The behavior of `%{?builtin_macro:foo}` is unclear from documentation (Issue #1866)

[Vít Ondruch]

> Well, good to have that cleared because it wasn't clear to me at all what this is about.

I think it was not clear what is going on, when RPM suddenly starts to complain about some file (while it was merely expansion of the argument after all). Again, this would not happen for other builtins, which are typically used as part of some expression and not at the beginning of the line.

> In >= 4.17 you can generally use a macro without having to care whether its built-in or user-defined, eg "%load foo" will try to load file "foo" as you'd expect.

Ah, this is very nice, step in the right direction. That could have simplify the RHEL7 compatibility, where we are still using the original LUA implementation.

> There are some inconsistencies left in 4.17.0

Yep, apparently `%{?load %{SOURCE4}}` is missing argument :)

So probably lets keep the status quo for the moment. Thx for all the insights :+1: 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1866#issuecomment-996571946
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/1866/996571946 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20211217/bae0af07/attachment.html>