Mmm... You are right, of course. It's been some time, since I've created the
patch and apparently I have forgotten the details.
Anyway there are many configure-like scripts that accept
--enable-/--disable-/--with-/--without- options, not necessarily generated with
autotools. I have found
Signed-off-by: Ćukasz Stelmach
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/176
-- Commit Summary --
* Add macros to generate --enable-/disable- arguments
-- File Changes --
M macros.in (3)
To generate arguments for configure scripts. Take a look a few lines above at
%{with}/%{without} macros. My macros do exactly the same but for
--enable-/--disable-.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> I think the problem here is that these macros do use the same name for both
> the bcond variable and the configure switch.
You are right. Gentoo has
[`use_enable`](https://gitweb.gentoo.org/proj/portage.git/tree/bin/ebuild.sh?id=033e7b68cc5495ab43498a73940be23b919aa5cf#n254)
and
Look above and you will find that naming was and still is my concern.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/2441
-- Commit Summary --
* Conditionally display VCS tag
-- File Changes --
M rpmpopt.in (1)
-- Patch Links --