Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to use cached packages #1030

Closed
smaudet opened this issue Feb 29, 2020 · 2 comments
Closed

Option to use cached packages #1030

smaudet opened this issue Feb 29, 2020 · 2 comments

Comments

@smaudet
Copy link

smaudet commented Feb 29, 2020

This is a buildozer feature request.

You are currently downloading every single package every time a buildozer folder is removed and rebuilt from spec. I am currently trying to troubleshoot a broken recipe, meaning I am hitting these servers multiple times. My internet is fine, however this all costs $$$ - I don't think you intended to but you built a poorly coded DDOSing tool.

To be clear, I mean there should a) be indication that although a particular url would be fetched, it won't, and instead a cached local package (maybe in ~/.buildozer) is used in its place. Not making any recommendation to do hash checking, but I suspect you could even fetch packages from pip's repositories? b) provide some option to re-download a particular package. A tree would be nice here so you know which packages depend on which others in case of corruption.

This is contrast to today where the only cache seems to the local .buildozer folder.

Please consider adding more to the docs for troubleshooting or cleaning builds and/or update buildozer so that it caches packages instead of constantly (re) downloading them.

@xandro0777
Copy link

Apparently #801 might address this?

@Julian-O
Copy link
Contributor

This is being closed, but not forgotten. It has been consolidated into issue #1727.

@Julian-O Julian-O closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants