freetype: use libpng version range #23004
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
freetype: all versions
Use a version range for libpng in requirements. This avoids version conflicts when libpng is consumed transitively, since most of the repo is still in
1.6.40
rather than1.6.42
.It's a rather artificial conflict when it happens -
libpng
is backwards compatible at the API level, and Conan 2 defaults (theminor
version component is encoded in the consumers) will ensure binary compatibility of produced binaries (e.g.libpng/1.6.x
may not necessarily be binary compatible withlibpng/1.5.x
, but .patch versions of the same minor will be).libpng
changes the library filename and soname when jumping to new minors. The default documented behaviour https://docs.conan.io/2.0/reference/conanfile/attributes.html#package-id-embed-non-embed-unknown-mode should ensure that new binary packages are generated in that case if libpng is updated.