Kristoffer Carlsson

Does ```jl using UUIDs, Pkg registries = Pkg.Registry.reachable_registries() d = Dict{UUID, Set{VersionNumber}}() for registry in registries uuids_with_name = Pkg.Registry.uuids_from_name(registry, "Pluto") for uuid in uuids_with_name pkg_info = Pkg.Registry.registry_info(registry[uuid]) d[uuid] = keys(pkg_info.version_info)...

Not really, but you can use the https://github.com/GunnarFarneback/RegistryInstances.jl package: > The whole purpose of RegistryInstances is to provide the RegistryInstance abstraction without relying on Pkg internals.

How do we get the dependencies for that stdlib then, to put in the manifest?

> But that additionally requires an API to convert a module or package name to its UUID. So you only want to query something that is a direct dependency? Otherwise,...

Oh, I thought you just wanted to know how to do it. I guess a one-line wrapper around `Pkg.dependencies` could be added to Pkg, although it feels maybe a bit...

As been said, this already exists. A PackageSpec is not really suitable because that cant eg hold a git tree sha. Is what is needed a way to lookup a...

I don't think we ever precompiled a registry update. But it looks like there is significantly more compilation now, indeed. 1.7: ```jl pkg> activate --temp julia> @time Pkg.update() ... 1.902799...

Mine too. Why would it not read the tarball?

Yes but first, you are not calling `Pkg.Registry.update` but the normal update which uses the resolver etc. And even for `Pkg.Registry.update` we call `reachable_registies`: https://github.com/JuliaLang/Pkg.jl/blob/13b7861518dcfceebfc01566c329a2b2faa62623/src/Registry/Registry.jl#L343 which "materializes" the registry.

That also uncompresses the registry because it eagerly collects the registries when creating a `Types.Context`. Should probably be changed to only do that when using it...