You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I use piece-wise boost ports, explicit versioning in vcpkg.json (rather than relying on baseline commit hash in registry configuration), and the result is that boost port versioning is a huge mess.
Notice that some parts of boost are resolved to version 1.80.0, and some are resolved to version 1.79.0. The reason is that my baseline hash contains boost @ 1.79.0, while my explicit dependencies (boost-icl, boost-program-options, boost-circular-buffer) are set to require version 1.80.0.
Proposed solution
Boost packages should depend on each other with version constraints. e.g. boost-icl's vcpkg.json should look like this
If an end user still needs to use a boost part at specific older version, they can use override to achieve that, but mixing & matching boost versions CAN'T BE THE DEFAULT BEHAVIOUR.
The text was updated successfully, but these errors were encountered:
Actually this is a design issue across all vcpkg ports.
If I don't update baseline, all my transitive dependencies are stuck at the version they were when I picked baseline. If I update baseline, it will happily override my explicit version constraints by adding higher ones of its own.
Is your feature request related to a problem? Please describe.
I use piece-wise boost ports, explicit versioning in
vcpkg.json
(rather than relying onbaseline
commit hash in registry configuration), and the result is that boost port versioning is a huge mess.This is my (a part) of the resolved port set:
Notice that some parts of boost are resolved to version 1.80.0, and some are resolved to version 1.79.0. The reason is that my baseline hash contains boost @ 1.79.0, while my explicit dependencies (
boost-icl
,boost-program-options
,boost-circular-buffer
) are set to require version 1.80.0.Proposed solution
Boost packages should depend on each other with version constraints. e.g.
boost-icl
'svcpkg.json
should look like thisIf an end user still needs to use a boost part at specific older version, they can use override to achieve that, but mixing & matching boost versions CAN'T BE THE DEFAULT BEHAVIOUR.
The text was updated successfully, but these errors were encountered: