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

Document the interpretation of compat ranges in registries #1349

Merged
merged 4 commits into from
Jun 7, 2023

Conversation

timholy
Copy link
Member

@timholy timholy commented Sep 3, 2019

This is a start on #1190. @StefanKarpinski or others, feel free to modify at will.

@KristofferC
Copy link
Member

This might get obsoleted by #1410 where we also have the same hyphen compat specifier as the registry uses.

@nickrobinson251
Copy link
Contributor

Bump?

@timholy
Copy link
Member Author

timholy commented Mar 4, 2020

Presumably this can be closed due to https://julialang.github.io/Pkg.jl/dev/compatibility/#Hyphen-specifiers-1, right?

@nickrobinson251
Copy link
Contributor

nickrobinson251 commented Mar 4, 2020

Do hyphen ranges in a Project.toml and a registry's Compat.toml have the exact same semantics?

And the exact same valid syntax? e.g.

"0.7-0.8"  # [0.7.0, 0.9.0)
"0.7-0"    # [0.7.0, 1.0.0)
"0.8.6-0"  # [0.8.6, 1.0.0)
"0.7-*"    # [0.7.0, ∞)

is this valid syntax for a Project.toml?

If yes to both, can we just document that?

But don't non-hyphen range have a different meaning?
E.g.

# F/Foo/Compat.toml

["0.18.2-0.19"]
Bar = "0.5.0"

means Foo version [0.18.2, 0.20) allows only the exact version 0.5.0 of dependency Bar (and not e.g. Bar v0.5.1)?

Caveat: I do not understand Registry syntax, so these are all questions. Personally I've only need to understand registry syntax when the registry has been manually edited and accidentally introduced an error (which i've then tried to debug, by trying to read the registry)

@KristofferC KristofferC added the merge me Merge when tests pass label Jun 7, 2023
@KristofferC KristofferC merged commit edc137f into master Jun 7, 2023
@KristofferC KristofferC deleted the teh/doc_compat branch June 7, 2023 14:50
@DilumAluthge DilumAluthge removed the merge me Merge when tests pass label Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation registries Pkg's handling of package registries
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants