I think the original intend was to make the macro definitions look like bash
function definitions.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2976#issuecomment-2031386866
You are receiving this because you are subscribed to this
The code in doDefine() supports multiline macros, it's that nasty rdcl()
function that is to blame here.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2976#issuecomment-2031383183
You are receiving this because you are subscribed to
I certainly remember seeing that code, but never quite got what it actually
refers to. I doubt anybody knows of it, really.
It'd be a lot more useful if it permitted multiline macros. People seem to be
widely abusing %{expand:...} (probably without fully realizing the
consequences) to get the
Relevant piece of code:
https://github.com/rpm-software-management/rpm/blob/c4665da3b6f9adc1e689e77fdf83c91b264be40f/rpmio/macro.c#L722
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2976#issuecomment-2020965004
You are receiving this
I noticed that there is no documentation for this construct
```
$ rpm --define 'foo { bar }' --eval '>%{foo}<'
> bar <
```
Should we document it? Or is that feature deprecated? Does anybody use it at
all?
--
Reply to this email directly or view it on GitHub:
