Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add versioning support for Vcpkg ports. #114

Open
angelfor3v3r opened this issue Jun 25, 2023 · 0 comments
Open

Add versioning support for Vcpkg ports. #114

angelfor3v3r opened this issue Jun 25, 2023 · 0 comments

Comments

@angelfor3v3r
Copy link

Vcpkg ports support versioning.

It seems like the current official way of listing versions is to run a git command line git blame -l versions/<port-first-char>-/<portname>.json. There's also 3rd party sites such as this one that display version history.

I'm not sure what the best way is to go about implementing this, but I think we can do a syntax like [“<port name>[<features, here>]==<version number>#<port version>"]. A more specific example would be ["imgui[dx9-binding, freetype]==v1.89.6#1 which means imgui with dx9-bindings, freetype features, version v1.89.6 and port #1.

It seems like Vcpkg supports having dependencies with a version key inside. The builtin-baseline brings in ports with that version number at the time of the commit and Vcpkg will decide if it satisfies the minimum version specified in the version key. But then it gets a bit more complicated because you can specify older versions using the overrides key, with names and versions inside that too.

There's a lot of information about them here.

At the moment, the only way to use old versions is to specify old commit tags/hash, which I assume isn't ideal if you want to lock to specific port versions, and it might be missing newly added ports too.

If I'm misunderstanding how Vcpkg versioning works, please let me know so I can update the issue. So far, this sounds like a huge hassle to support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant