From 504add3efbc03a7ca6438240ef0dc86b67671817 Mon Sep 17 00:00:00 2001 From: Petr Viktorin Date: Fri, 29 Jan 2021 14:45:59 +0100 Subject: Remove `_with_*` from the documentation This section uses the `_with_*` macro, which is dangerous when used in combination with `%bcond` or `%bcond_without` because it doesn't honor the "default". The section above already explains what users should do -- some variation of: %{?with_gnutls:--with static} \ %{!?with_openssl:--without openssl} ... which is more verbose, but works with %bcond` & `%bcond_without`. (cherry picked from commit 1c2970dda2c828b07fcaec494b9f5abe01ed8cb0) --- docs/manual/conditionalbuilds.md | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/docs/manual/conditionalbuilds.md b/docs/manual/conditionalbuilds.md index a2d913967..bcf8bdeb1 100644 --- a/docs/manual/conditionalbuilds.md +++ b/docs/manual/conditionalbuilds.md @@ -83,16 +83,5 @@ macros which is nicer in other situations, e.g.: Always test for the `with`-condition, not the `without`-counterpart! -## Pass it to `%configure` - -To pass options to configure or other scripts that understand a `--with-foo` or -`--without-foo` parameter, you can use the `%{?_with_foo}` macro: - -``` -%configure \ - %{?_with_gnutls} \ - %{?_with_openssl} -``` - ## References * [macros](https://github.com/rpm-software-management/rpm/blob/master/macros.in) -- cgit v1.2.1