Keep, clean, and remove releases

[mirror-shades]

Keep/Clean Releases

Description

Added commands to manage which Zig versions are kept or removed from cache

Changes

• Added new subcommands:
  • any keep VERSION: Prevents a version from being removed
  • any clean: Removes all non-kept versions
  • any force-remove VERSION: Force removes a version (bypasses keep)
• Added persistent keep markers using keep files in version directories
• Enhanced list-installed to show kept status
• Added utility functions:
  • keepCompiler() - Creates keep markers
  • cleanReleases() - Cleans non-kept versions
  • removeRelease() - Handles version deletion
• Improved error handling for concurrent operations

Testing

• Verified functionality on windows and arch linux (x64)

Notes

• Keep system helps prevent accidental removal of important versions
• Clean command helps manage cache size while respecting kept versions
• Force-remove provides a method of removing kept versions
• Similar keep file implementation to Zigup

[marler8997]

We seem to be lacking a normal "remove" command to remove a compiler that's not been marked to keep. I'm not sure we need a distinction between removing a version that's been marked to keep or not, if the user has explicitly asked anyzig to remove a specific version, I think we can infer they no longer want to keep it. With that, we could implement all the use cases by enhancing clean to take an optional version (or versions...).

[mirror-shades]

There is a force-remove command which removes a single version regardless of its keep status. I chose force-remove only to be more explicit that it doesn't check for keep files, so in this case the fix should just be a matter of changing the command name. I can do that tonight. Or would you prefer a single command clean with optional arguments? I like more explicit commands but I understand wanting to keep the api simple

[marler8997]

I think I'd prefer just one command with optional arguments.

zig any clean [VERSIONS....]

[mirror-shades]

Should be working as expected now

[marler8997]

We should store the keep files in anyzig's appdata directory, not in zig's global cache directory.

[mirror-shades]

is there any specific value in having the keep file outside of the release folder? by my eyes the current implementation actually makes the removal process a bit simpler

[marler8997]

I'm not sure what you mean by "release folder"? You're storing the keep files in zig's global cache which horribly breaks how zig's caching system works. You've modified the contents of a "content addressable store"...which...would mean you'd need to change the path of what you're storing because you changed it's content.

It's the same idea as modifying the contents of a git commit and without updating the commit hash.

[mirror-shades]

Oh I see, I had some false assumptions about how the caching system works. I thought it was specific to the executable, not the folder contents. This makes a lot of sense, I will have to rework.

[mirror-shades]

Let me know what you think about this implementation. It now creates/finds a kept-releases folder in the anyzig data folder to store keep files.