[New Port Request] <library name here>

[qinchuan-dev]

Library name

etcd-cpp-apiv3

Library description

c++ etcd client library

Source repository URL

https://github.com/etcd-cpp-apiv3/etcd-cpp-apiv3

Project homepage (if different from the source repository)

No response

Anything else that is useful to know when adding (such as optional features the library may have that should be included)

https://github.com/etcd-cpp-apiv3/etcd-cpp-apiv3 is the only active maintained repo which provides "etcd" cpp client. Please add this lib to vcpkg.

[ChrisSchulte]

I'm confused as the port for etcd-cpp-apiv3 v0.15.4 has been done and was published in tag 2025.02.14 but disappeared in tag 2023.03.19. The version file still exists and I was able to perform a vckpg install in manifest mode of the port. I don't know how it works, but the port seems to exist. After install the portfile and vcpkg.json file appear in path .\buildtrees\versioning_\versions\etcd-cpp-apiv3\294ed70c0aa28d439d90290e0b4eb2a4ba4bf4c5. Maybe a vcpkg maintainer (@dg0yt as you seem to have a deep knowledge of how vcpkg works ) could explain how it works ?

[dg0yt]

was published in tag 2025.02.14 but disappeared in tag 2023.03.19 2025.03.19

"etcd-cpp-apiv3" is in the version registry up to "0.15.4#3":
https://github.com/microsoft/vcpkg/blob/2025.03.19/versions/e-/etcd-cpp-apiv3.json
This is how it is resolved in manifest mode: Fetch the git-tree ref from the versions database, and then fetch the port recipe from that ref.

However, it was "delisted" in #42678 because it prevented the update of the boost ports. (Note that this PR was pending for three months. Some other ports share this fate.) vcpkg CI operates in classic mode, and there is no point in advertising ports which can't be tested and used in classic mode.

When upstream resolves the boost issues and makes a release, it should be easy to bring that port back.