Closed #815.
--
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/pull/815#event-2556286671___
Rpm-maint mailing list
Um, rpm macros have nothing to do with m4.
I don't have any concrete proposals at this time, just asking for a rethink and
pointing to the general direction that I would find acceptable.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
> I'm really reluctant to add one-trick-pony utility macros like this because
> over time they tend to become liabilities one way or the other, and have
> other issues.
Good.
>
> Manipulating compiler flags is a very common need indeed and could use some
> help from rpm, but that need is not
I'm really reluctant to add one-trick-pony utility macros like this because
over time they tend to become liabilities one way or the other, and have other
issues.
Manipulating compiler flags is a very common need indeed and could use some
help from rpm, but that need is not limited to
@marxin Why is this necessary?
--
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/pull/815#issuecomment-521185369___
Rpm-maint mailing
The macro function is intended for %{optflags} manipulation
(replacement, conditional addition).
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/815
-- Commit Summary --
* Come up with replace_optflags (#814).
-- File
