As per above, it's not a legitimate character in *rpm* filenames, and the
macros do not deal with binary data. I don't see a need to complicate things
for this.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #1438.
--
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/1438#event-4210962557___
Rpm-maint mailing list
It's not legit in *rpm* filenames though. See
https://github.com/rpm-software-management/rpm/blob/c1ca2e35025698328edcefa8dedee866d2ea0596/build/files.c#L1329
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Indeed it is, but not being able to write `quote_array` is somewhat concerning,
especially since `\x1a` is technically a valid character in filenames.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Rpm macro engine is just a very simple-minded text processor. Handling binary
data is out of scope.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Right now, I cannot write a Lua function `quote_array` that converts an array
of strings to a string that (when used as the argument to a macro) will be
interpreted as the initial array. This is because \\x1a (ASCII unit separator)
cannot be escaped.
One solution would be to allow \\x1a to be
