I have noticed that,following a zvm install command, zvm removes all directories containing versions of zig that are not in the list of the available ones.
It would be nice if it would keep them installed because it would let one track some specific dev versions that one may want to stick to for some reason.
For a real life use case, see MicroZig that, at the moment, requires its users to use Zig 0.17.0-dev.1158+1d1193aa7, which is not the latest dev build.
Steps to reproduce:
- Download any "dev" build of Zig.
- Unpack it in the
~/.local/share/zvm directory.
- Run
zvm ls and the bespoke version is in the list of the installed ones.
- Run
zvm install master (or any other "available" version) and the directory with the bespoke dev build gets removed.
If that was the version in use the bin link that pointed at is now also broken.
I have noticed that,following a
zvm installcommand, zvm removes all directories containing versions of zig that are not in the list of the available ones.It would be nice if it would keep them installed because it would let one track some specific dev versions that one may want to stick to for some reason.
For a real life use case, see MicroZig that, at the moment, requires its users to use Zig 0.17.0-dev.1158+1d1193aa7, which is not the latest dev build.
Steps to reproduce:
~/.local/share/zvmdirectory.zvm lsand the bespoke version is in the list of the installed ones.zvm install master(or any other "available" version) and the directory with the bespoke dev build gets removed.If that was the version in use the
binlink that pointed at is now also broken.