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

[vcpkg] Rename port_versions to versions #15784

Merged
merged 2 commits into from
Jan 21, 2021

Conversation

strega-nil
Copy link
Contributor

After bikeshedding, we have decided upon a different name for the existing port_versions directory and we want to rename it before people start depending on it.

@strega-nil strega-nil force-pushed the port_versions-bikeshedding branch 3 times, most recently from e7eb104 to 42e0708 Compare January 21, 2021 00:25
@strega-nil
Copy link
Contributor Author

Only review the second commit, the first one is literally just a rename of port_versions to versions.

@@ -319,9 +319,9 @@ Although the concept of package versions has always been present in vcpkg, the c

With the introduction of versioning constraints, it is now possible that a package depends on a port version that does not match the one available locally. This raises a problem as vcpkg needs to know how to acquire the port files for the requested version.

To solve this problem, a new set of metadata needs to be introduced. This specification proposes a that a new “port_versions” folder is added as part of a registry. In the main vcpkg registry, this means a new root level port_versions directory.
To solve this problem, a new set of metadata needs to be introduced. This specification proposes a that a new "versions" folder is added as part of a registry. In the main vcpkg registry, this means a new root level versions directory.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

directory, not folder. (Sorry, I know you didn't edit, but still)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

prolly not gonna make that change since I'm just doing the boring rename thing.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only worry about it if you need to spin this again. (I view this comment as no different than you asking me to sort cmake vars in the vcpkg_minimum_required PR :) )

@strega-nil strega-nil force-pushed the port_versions-bikeshedding branch 2 times, most recently from d355de4 to 9f300b1 Compare January 21, 2021 00:44
@JackBoosY JackBoosY self-assigned this Jan 21, 2021
@JackBoosY JackBoosY added category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed info:internal This PR or Issue was filed by the vcpkg team. labels Jan 21, 2021
@strega-nil strega-nil force-pushed the port_versions-bikeshedding branch from 9f300b1 to 44d4e36 Compare January 21, 2021 00:55
@strega-nil
Copy link
Contributor Author

Thanks @vicroms

@strega-nil strega-nil force-pushed the port_versions-bikeshedding branch from d1aef5d to 4615477 Compare January 21, 2021 17:00
@strega-nil strega-nil force-pushed the port_versions-bikeshedding branch from 4615477 to d5c6ad8 Compare January 21, 2021 17:52
@strega-nil strega-nil merged commit 68a7495 into microsoft:master Jan 21, 2021
strega-nil added a commit to strega-nil/vcpkg that referenced this pull request May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed info:internal This PR or Issue was filed by the vcpkg team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants