Kristoffer Carlsson
Kristoffer Carlsson
> This sounds fantastic. Is this a feature that would be available in a Julia 1.x release, e.g. Julia 1.4 or Julia 1.5? Or would it have to wait until...
Triaging to discuss what to do about multiple conditional dependencies (which kind of starts to sound like "features").
AFAIU, the difference between features and conditional dependencies is that a feature is something that someone opts into from the current active Project while a conditional dependency is automatically "activated"...
We need to be able to give `compat` info. How about making the glue packages look a lot like a "mini package" but each glue package is under a glue...
True, I'll try reformulate it.
Tweaked the wording a bit. Also added "may" to the green `^` symbol to make it clearer that it is not 100% the package can be upgraded. cc @IanButterworth
When you think this is ready, it would be good with a bit of a higher level description of what this implements and how it works etc. Just to aid...
> Alright. In which cases is Pkg "allowed" to look at the source field? Whenever tracking a package by path or url maybe?
That's in the manifest though. But yeah, that's a good idea as well. Also, I notice that Cargo stores the URL to the registry where the information for the package...
The API (while still internal) should be better in 1.7. It would be something like: ```jl using UUIDs registry = Pkg.Registry.RegistryInstance("/home/kc/.julia/registries/General") uuids_with_name = Pkg.Registry.uuids_from_name(registry, "Pluto") d = Dict{UUID, Set{VersionNumber}}() for...