How do I pin the version of feature's dependency?

[cuiy0006]

Our package google-cloud-cpp is not compatible with the latest version of opentelemetry-cpp v1.2.1.

It is a dependency of a feature of our package.

I didn't find any way to pin the version to v1.2.0.

I tried with "version>=": "1.20.0", but seems there is no "<=" or "=" for the purpose.

I tried with

"builtin-baseline": "9845848c2af843cdad92bd407cebd390b13db553",
  "overrides": [
    {
      "name": "opentelemetry-cpp",
      "version": "1.20.0"
    }
  ],

But seems it doesn't work to pin the version of feature dependency.

$ ./vcpkg remove google-cloud-cpp && ./vcpkg install google-cloud-cpp[opentelemetry] --dry-run
The following packages are not installed:
    google-cloud-cpp:x64-linux
Computing installation plan...
The following packages will be built and installed:
    google-cloud-cpp[bigquery,bigtable,core,grpc-common,iam,monitoring,opentelemetry,pubsub,rest-common,spanner,storage,trace]:x64-linux@2.37.0
  * opentelemetry-cpp:x64-linux@1.21.0
Additional packages (*) will be modified to complete this operation.

Please help figure out how to pin the opentelemtry-cpp version to 1.20.0.

[Osyotr]

You can try adding a registry with just this port and desired baseline:

{
  "$comment": "opentelemetry-cpp 1.2.0",
  "kind": "git",
  "repository": "https://github.com/microsoft/vcpkg",
  "baseline": "2924f54a2c3ac701a92e0c78c13aca7111ecb3ed",
  "packages": [
    "opentelemetry-cpp"
  ]
},

[cuiy0006]

Thank you for answering my question!

Based on your comment and https://learn.microsoft.com/en-us/vcpkg/consume/git-registries, I made the change.

I noticed when I run vcpkg add port opentelemtry-cpp, it adds opentelemetry-cpp in root dependency instead of feature's dependency.

The baseline I chose has opentelemetry-cpp 1.20.0.

But I still get opentelemetry-cpp 1.21.0 in dry run mode.

$ ./vcpkg install google-cloud-cpp[opentelemetry] --dry-run
Computing installation plan...
The following packages will be built and installed:
    google-cloud-cpp[bigquery,bigtable,core,grpc-common,iam,monitoring,opentelemetry,pubsub,rest-common,spanner,storage,trace]:x64-linux@2.37.0
  * opentelemetry-cpp:x64-linux@1.21.0
Additional packages (*) will be modified to complete this operation.

Did I miss anything in my configuration?

[autoantwort]

You don't use manifest mode if you can specify any port names on the command line. Where is your vcpkg.json file and where do you execute vcpkg?

[cuiy0006]

1. Yes, I didn't run the above commands in manifest mode.

2. I am trying in manifest mode now.

$ ../../vcpkg install --dry-run
...
git+https://github.com/microsoft/vcpkg@060c829772d52e920fee94cf84755031c61e3b67
    openssl:x64-linux@3.5.0#1 -- git+https://github.com/microsoft/vcpkg@6819498ce6c5c3e379b3ffbd2b5d93e3fc271933
    opentelemetry-cpp:x64-linux@1.20.0 -- 
...

Yes, it is using opentelemetry-cpp 1.20.0 in manifest mode. Thank you for the answer!

I have one more question, if the classic mode doesn't pick up vcpkg-configuration.json, the command vcpkg install will always fail because it is using opentelemetry 1.21.0. Is there any way to make classic mode work with vcpkg-configuration.json?

[Osyotr]

In Classic Mode, vcpkg will use the vcpkg-configuration.json file in the root of the vcpkg instance.

https://learn.microsoft.com/en-us/vcpkg/reference/vcpkg-configuration-json