Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=689709
--- Comment #11 from Iain Arnell iarnell@gmail.com 2011-03-23 08:52:32 EDT --- (In reply to comment #10)
I am insisting on bcond_without, because
our interest is Fedora, a distro which is incrementally built and want to test our packages "to the max" as part of our regular works whenever we build our packages.
i.e. people who are trying to bootstrap from scratch for whatever reasons, are not of any importance and need to be taught that Fedora is incrementally built. Apart of perl, they will be facing similar issue all over the place, e.g. when building gcc/glibc/kernel (also an incrementally built system).
I agree entirely with the argument. Rebuilders who need this should be forced to add --with bootstrap. But the bcond magic to do that is bcond_with, not bcond_without:
# Handle conditional builds. %bcond_with is for case when feature is # default off and needs to be activated with --with ... command line # switch. %bcond_without is for the dual case. # # %bcond_with foo defines symbol with_foo if --with foo was specified on # command line. # %bcond_without foo defines symbol with_foo if --without foo was *not* # specified on command line.