Revamp zig build caching #1881
Merged
Revamp zig build caching #1881
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now split the cache into the zig global cache and the zig local cache. Zig had these separate from the beginning but as Zig didn't differentiate between them earlier, before the package manager, I didn't know what they were good for and so we ended up just using a single directory. Now that there is a package manager, we separate the global cache, which is used for downloaded packages, and the local cache which is used for built stuff. The automatic clearing of the cache is kept but only applies for the local cache. The global cache is never automatically cleared, instead a warning is emitted once it crosses 10GB in size and for every additional 1GB in growth.
plajjan
force-pushed
the
zig-cache-revamp
branch
from
2f61f10
to
289e079
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now split the cache into the zig global cache and the zig local cache. Zig had these separate from the beginning but as Zig didn't differentiate between them earlier, before the package manager, I didn't know what they were good for and so we ended up just using a single directory. Now that there is a package manager, we separate the global cache, which is used for downloaded packages, and the local cache which is used for built stuff.
The automatic clearing of the cache is kept but only applies for the local cache. The global cache is never automatically cleared, instead a warning is emitted once it crosses 10GB in size and for every additional 1GB in growth.
Fixes #1858