Leave bad enough alone imho.
Every macro templating language in the world has quoting problems: its the
nature of the beast.
And a Principle of Least Surprise "Do what bash does!" sets expectations that
are wildly out of line with reality.
FWIW, the only place that macros MUST be used (instead
Related to https://fedoraproject.org/wiki/Changes/Platform_Python_Stack
The changes are "backwards compatible" - i.e. it does not break systems without
Platform Python. (Except in a rare case when someone would install to
/usr/lib(64)?/platform-pythonX.Y without having a Platform Python.)
Not s
Hello, @proyvind
I am not a maintainer of this project.
However this project started to use CI recently.
So, it might be good to rebase your branch for PR on top of master branch.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitH
Examples of stuff that broke:
https://bugzilla.redhat.com/show_bug.cgi?id=1481025
https://bugzilla.redhat.com/show_bug.cgi?id=1481133
--
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/
@mlschroe and others too of course: ideas welcome...
--
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#issuecomment-322135297
Reopened #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-1204413195___
Rpm-maint mailing list
Rpm-maint@lists.r
So... this is not going to fly, too many macros rely on quotes passing
untouched (and why shouldn't they, that's the way its been all this time).
We'll need some other kind of solution that's opt-in one way or the other.
Reopening.
--
You are receiving this because you are subscribed to this t
