validate docs #1947
validate docs #1947
Conversation
| raise ConanInvalidConfiguration("Option 2 of 'dep' not supported") | ||
|
|
||
|
|
||
| If a package uses ``compatible_packages`` feature, it should not add to those compatible packages configurations that will not be valid, |
There was a problem hiding this comment.
In this section, I think it is more important to show how a compatible package (a valid one) will be used to substitute an invalid package. Something with the compiler.cppstd is very evident: the package is invalid (will fail with conan create) if using C++11, but a conan install will use a compatible one that was built using C++14,17,20.
These comments about what packages to add to self.compatible_packages belong to the documentation of the compatible_packages feature.
There was a problem hiding this comment.
But this is also a valid use case, in which you can fallback to release artifacts in Linux if you don't have the debug one, which usually works in non-windows platforms. I am not sure if I understand the issue.
There was a problem hiding this comment.
Not an issue, I think that the other use case is much more interesting regarding validate + compatible-packages. Falling back to Release builds I think it is more related to compatible-packages than validate, and this is the documentation for the validate function. One example is enough, the other is better IMO.
Docs for conan-io/conan#8053