Hi all, if I read the docs[1] correctly, it is enough for a %_with_XXX feature to be defined, the value does not matter. So setting it to 0 does not disabled it. TL;DR: Is it possible to to un-define a %_with_XXX at project level in the prjconf? I already tried defining %_without_XXX, but that did not work, apparently as %_with_XXX was still defined. In my case I am trying to package some rubygems for SLES15/Leap15 using a newer ruby. I managed to get the ruby to be co-installable without causing harm, and if I drop large parts of the rubygems-gem2rpm spec file, I get building packages. But as the rubygems-gem2rpm spec file has these nice little %bcond_with_ruby21 and "%if %{with ruby21}" things, I tried to built without touching it. I succeeded in getting some packages to build by just building for ruby21 and ruby31, but as soon as a package requires ruby > 2.5 it falls apart. Hence my question: Can I un-define or disable a %_with_ruby21 or similar at project level? Or do I need to modify the spec file? Kind Regards Johannes [1] https://en.opensuse.org/openSUSE:RPM_conditional_builds https://en.opensuse.org/openSUSE:Build_Service_prjconf#%25bcond -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537