On Wed, Dec 2, 2015 at 6:44 AM, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
On Tue, 2015-12-01 at 18:56 -0500, Greg Freemyer wrote:
- if I hard code "%bcond_without protobuf_python" then the python bindings subproject is built. In plain english, what does %bcond_without mean?
Read it as 'Build conditionally without' - so only if somebody passes --without to the build process, it will be built without. The default behaviour is 'with' in this case.
This is not important to the fix, but I'm still trying to grok the syntax. Note that with: %bcond_with protobuf_python no python binding subpackage is built. While with: %bcond_without protobuf_python a python binding subpackage is built. That seems like there is double negative logic in place and only the first negative is reflected in the above. Is this a specific double negative logic implementation in protobuf.spec, or is bcond always used with a double negative type logic. Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org