Um, yes, many of the doFoo() routines re-expand the substituted text.
How exactly do you expect recursive substitution to Just Work if that was not
happening?!?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
An update, I've contacted the maintainers of the internal signing service to
obtain information about the rpm version used by their system to sign packages.
I'll post an update as soon as I hear from them.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
(duplicating first comment to generate mail to rpm-maint)
Watch this:
```
$ rpm --define '%xxx /hello//world' --eval '%xxx'
/hello/%%/world
$ rpm --define '%xxx /hello//world' --eval '%{shrink:%xxx}'
/hello/%/world
$ rpm --define '%xxx /hello//world' --eval '%{dirname:%xxx}'
/hello/%
--
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/313___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
But isn't that going to break lots of existing scripts? I don't see the harm of
allowing non-array tags like %{NAME} in array queries. (I.e. automatically add
a '=' for non-array tags.)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
Closed #222.
--
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/222#event-1229211727___
Rpm-maint mailing list
Since there are no nice quote characters left, implemented with the help of a
special %{quote:...} macro. It might not be the prettiest solution in existence
but at least it makes it *possible* to quote the arguments without stepping on
any existing uses I'd hope.
--
You are receiving this
