Open atomicflag opened 3 years ago
This option should never have been added in the recipe. Actually it should be completly removed.
That would work for us too. In fact, as a workaround, we are packaging the upstream conanfile in our private repo and it works exactly as we hoped it would. I was quite puzzled when I discovered that conan-center's conanfile deviates so much from the upstream version to the point where we can't use it in our project.
Also, a minor nitpick: https://github.com/conan-io/conan-center-index/blob/a836ab2cad1e57719f31f132076182056393ac5a/recipes/gsl-lite/all/conanfile.py#L12
("GSL")
is not a tuple, ("GSL",)
is.
Hi there! Sorry to catch up so late. I've created a PR https://github.com/conan-io/conan-center-index/pull/25157 which aims to address your old request.
Package and Environment Details
The version of the conanfile.py in this repo differs quite drastically from the upstream version, specifically we found that we can't use the conan-center version because it requires a user to choose a contract violation behavior upfront whereas the upstream version does not. Our build system needs to be able to decide the violation policy for itself at a later stage because we reuse conan dependencies for all submodules and some submodules require a different violation policy from the rest.
I propose we add
None
to the list of valid values for theon_contract_violation
option and make it so thatconanfile.py
doesn't add any defines whenon_contract_violation
isNone
.