Hello, in order to provide a safe dual build mode for Tizen (Yocto and OBS) we need to clean up a few spec files. Maintainers support is required in that operation.
In particular, we have Macros which are misleading because they define a value which let to believe that the option is not activated while the sole existence of the variable is enough to activate/deactivate the option what ever is its value. The fact that %bcond_without xxxxx works at the opposite of what basic logic would expect, does not help. Best practice is to defined option variable via %bcond as it allows to read the default options in an easy way and they can be changed in the rpm command line and add a comment in the spec file. In order to show how complex some spec files are I have picked on murphy (no personal issue here , we just needed one example, :-) https://review.tizen.org/gerrit/#/c/28042/10/packaging/murphy.spec For more info of rpm behaviour see : https://en.opensuse.org/openSUSE:Build_Service_prjconf#Macros Thanks in advance for your support. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
