Kristoffer Carlsson

AFAIK, the only input that Pkg uses from PackageSpec is: `name`, `uuid`, `version`, `repo`. The rest are "filler" fields to be filled in when the package has been downloaded. So...

Is there any package in the environment that is upper bounding GLMakie to that version? If not, then the upgradable marker is shown.

My guess is this got changed based on https://github.com/JuliaLang/julia/pull/36434. If the docs are out of date, then they do need updating, indeed.

One issue is when running with `--project=...` in that case no Pkg code is run. So to also catch that you would need to implement this in Base.

In my original test implementation of installing during `using` I had that pressing `Y` would remember your choice (while `y` would not). But you would still have to make one...

Well, that's something that is up to the user. Just by installing a package (or doing an update), you are already opening yourself up to some level of possible maliciousness.

> If I use Pkg.Operations.find_installed to get the path where v6.2.0+5 is installed I get > `julia> Pkg.Operations.find_installed("GMP_jll", UUID("781609d7-10c4-51f6-84f2-b8444358ff6d"), Base.SHA1("40388878122d491a2e55b0e730196098595d8a90"))` > `"/home/mose/.julia/packages/GMP_jll/IA6Pi"` > but this directory doesn't exist: This is...

Here is what we use in MKLSparse https://github.com/JuliaSparse/MKLSparse.jl/blob/3957a665612c4454815a305d53866d35cded5873/src/BLAS/level_2_3/generator.jl#L40 coupled with https://github.com/JuliaSparse/MKLSparse.jl/blob/3957a665612c4454815a305d53866d35cded5873/test/test_BLAS.jl#L26-L32. Quite ugly but still.

This has literally been uninstallable for many years so I don't see what difference this will do in practice.

Looking at how long ago that issue was opened that didn't seem like too great of a plan. In the meantime improvements just accumulate on the master branch because it...