Dependency version range

[megalosandros]

Is there any way to specify a version range for dependencies? Let's say I want to specify a dependency on a package, and I'm happy with versions 1.0, 1.1, 1.2, etc., but not 2.0 and higher. At the same time, I want that when a new version of the package is published that matches the 1.* mask, this package is automatically downloaded. In Conan, I can specify a range or specify masks - is there such an option in vkpkg?

[autoantwort]

vcpkg does not backfill versions, so when there is a version 2.0 1.x versions are not added to vcpkg anymore.

[megalosandros]

Got it, thanks! Sad but true.

[megalosandros]

What if I don't want to add new 1.* versions, but I want the dependency to be tied to 1.* and not jump to 2.0 even after 2.0 appears in ports? And at this particular moment I don't know the exact version number of 1, I only know 1.*?

[autoantwort]

When you update your baseline you know the version of the dependency

[megalosandros]

Scenario. The product consists of many components. Each component is a separate vcpkg package. The components depend on each other in some way. Let's say component A depends on component B version 1.* The developer of component B makes changes to the interface and publishes his component with version 2.0 In order not to break the build, component A needs to continue to depend on component B version 1.* for some time and not switch to version 2.* But at the same time, component A wants to receive the latest versions of the other components - so it needs an updated baseline