Closed #582 via #1064.
--
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/582#event-3051477166___
Rpm-maint mailing list
...and perhaps there should be that primitive to entirely suppress macro
expansion (as per the %{literal:...} suggestion in #1049, which simply expands
to its literal, unexpanded argument. But as literal is a macro type now, maybe
that should be called %{verbatim:...} instead. Dunno.
--
You
Good question, which I think settles the name as well: the argument is a macro
name, so it's not the opposite of %{expand:...} at all but a specific thing
that in rpm terminology is known as the macro body, so why make this any more
complicated... lets just call it %{body:...} and be done with
Is the argument a macro name or some generic string? I.e. is it
`%{body:_builddir}` which should then return ` %{_topdir}/BUILD`? Or is it
`%{noexpand:%_builddir}` which then should only do one level of expansion? I
find the latter a bit weird.
--
You are receiving this because you are
One fairly obvious choice here would be %{noexpand:...} as the direct opposite
of %{expand:...}.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Quote/quoting is something entirely different (we already have %{quote:...} btw)
Still thinking %{body:..} is the least worst so far.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
What about "literal", "quote" or "quoted"?
--
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/582#issuecomment-484037803___
%{unexpand:…} is not terrible, but it makes me think of unexpanding that has
already been expanded, which is not what it's about. %{body:...} has the
benefit that it's the same exact term we use in documentation, so people know
exactly what it is.
--
You are receiving this because you are
@pmatilai `%{unexpand:…}`?
--
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/582#issuecomment-483977641___
Rpm-maint mailing
Actually I think this is a perfectly legit request, it's not something you can
currently do regardless of how many %-escapes you add and not invasive at all.
Something along the lines of:
```
%{body:}
```
...but I'm not particularly happy about the name "body" so other suggestions
welcome.
Just put enough `%%` in there. It seems quite invasive change without much
benefit.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
As seen in
https://github.com/rpm-software-management/rpm/issues/581
when you want to write some variable definition to a macro file, it gets
expanded by rpm. That usually does not matter but unfortunately, in some cases,
you really really want the expansion to occur when the file definition is
12 matches
Mail list logo
