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

On Julia 1.8.0-DEV, LocalRegistry restricted to v0.3.2 #50

Closed
BioTurboNick opened this issue Jan 30, 2022 · 3 comments
Closed

On Julia 1.8.0-DEV, LocalRegistry restricted to v0.3.2 #50

BioTurboNick opened this issue Jan 30, 2022 · 3 comments

Comments

@BioTurboNick
Copy link

Due to compat bounds, attempting to install LocalRegistry on Julia 1.8.0-DEV leads to a very old version being installed, v0.3.2.

I'm assuming this is just because v0.3.2 has an open-ended compatibility bound.

Would it be better to make the bounds open-ended? If people should be careful about using it on the nightly builds, perhaps a warning could be produced instead?

@GunnarFarneback
Copy link
Owner

LocalRegistry relies too much on the Pkg internals for open-ended compatibility to be credible but I acknowledge there are drawbacks to upper-bounding it too. The registry definitely needs to be retro-capped for the oldest versions. I suspect the best solution is to keep master open-ended and refer Julia nightly users to that, but it will take some discipline to get that right.

@GunnarFarneback
Copy link
Owner

The registry definitely needs to be retro-capped for the oldest versions.

JuliaRegistries/General#55389

@GunnarFarneback
Copy link
Owner

I've bumped master to 1.8. I don't really trust myself to be consistent if I try to have only master unbounded, so I'll see if this will actually cause problems. At least Julia master shouldn't pull in an old version anymore.

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