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

The "versions" field is misleading #55

Closed
jackfirth opened this issue Aug 15, 2017 · 1 comment
Closed

The "versions" field is misleading #55

jackfirth opened this issue Aug 15, 2017 · 1 comment

Comments

@jackfirth
Copy link
Sponsor

jackfirth commented Aug 15, 2017

The "Versions" field for editing a package implies its for specifying multiple different versions of the same package, and that a user can somehow pick a specific version to install / depend on or constrain the version using some semver-like system. But it's actually for version exceptions which provide different versions of the same package based on what Racket version a client is using. There are some packages who have confused it for the former, including the herbie package with "1.0" and "1.1" versions (which will never be used). Changing the field name to "Version exceptions" and maybe making it link to the appropriate docs about version exceptions might help.

@jeapostrophe
Copy link
Collaborator

Done, thanks.

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

No branches or pull requests

2 participants