juliaup gc should remove compiled and environments folders that are no longer needed

[numbermaniac]

I had Julia release 1.10.5 and beta 1.11rc3 both installed using Juliaup. I used juliaup remove release to remove the 1.10.5 installation, and then afterwards, used juliaup gc. To my surprise, the .julia/compiled/v1.10/ and .julia/environments/v1.10/ folders remained, which is significant because the first one was using 700MB of storage. I would've expected them to be deleted since they're no longer needed.

It would be great if juliaup gc could detect when such folders are no longer needed and remove them accordingly. Thank you!

(If it helps: Juliaup 1.17.4, macOS 14.6.1)

[davidanthoff]

My gut feeling is that we can/should do something about the .julia/compiled folder, but not .julia/environments. The compiled folder is really just a cache/optimization, so deleting that seems fine. But the environments folder is really user-controlled/created data, and I think we should just never delete anything there.

[KristofferC]

Should imo be a part of Pkg.gc since that already handles artifacts and packages.

[davidanthoff]

But Pkg.gc presumably doesn't know which Julia versions are installed, right?

[numbermaniac]

Yeah - I assume a Pkg in one Julia installation wouldn't know what other Julia installations you have, so it would need to be managed by juliaup.