- store cache about ~/.buildozer in ~/.buildozer and cache about .bui… #801
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
…ldozer in .buildozer
This was referenced Oct 4, 2021
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.
While hacking in buildozer, I discovered that cache in local .buildozer dir stores information about state of ~/.buildozer
It leads to situation, that when you remove local .buildozer file, in next buildozer run whole SDK and NDK (huge downloads) is downloaded again.
Also, it's possible that if you remove ~/.buildozer, then local cache still things that everything is still in ~/.buildozer and build fails.
This PR splits the cache.