On 03/01/2016 04:07 PM, Florian Festi wrote: > On 03/01/2016 03:51 PM, Michael Schroeder wrote: >> On Tue, Mar 01, 2016 at 03:29:41PM +0100, Florian Festi wrote: >>> On 02/29/2016 08:53 PM, Florian Weimer wrote: >>>> This protection is in the way if the --short-circuit -bb is used to >>>> build packages for testing the effects of complex dependency changes >>>> in a spec file. >>> >>> Would it be sufficient for your use case to change the anti-cheating >>> Requires to something other than an rpmlib() that could actually >>> provided by an "enable-cheating" package? Probbaly with adding the spec >>> file of such a package to the documentation? >> >> Or make the anti-cheating configurable with a rpm macro... > > or a command line switch > > --idkfa
I think doing non-Koji or non-Mock (or non-other-build-service) builds was firmly in this category already. That is, any direct invocation of rpmbuild. Specifying --short-circuit certainly is, it is unlikely to work if you have an existing build tree populated by a previous RPM-driven build, too. Florian _______________________________________________ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint