5 ms·
We had the same problems already in the 90s and resolved them by caching, it's unthinkable that the whole build is broken by a problem with an external dependen
by dvfjsdhgfv 5y ago
We had the same problems already in the 90s and resolved them by caching, it's unthinkable that the whole build is broken by a problem with an external dependence - if you assume everything will be 100% available you basically make sure a problem will happen.
- creshal 5y agohttps://wiki.debian.org/AptCacherNg https://wiki.debian.org/AptCacherNg still exists and still works fine.
- tambre 5y agoAptly [0] is also really nice for maintaining mirrors and one's own Apt repositories though it is unmaintained. [0]: https://github.com/aptly-dev/aptly https://github.com/aptly-dev/aptly
- silon42 5y agoNot caching... mirroring or vendoring.
- rkeene2 5y agoI wrote "hashcache" [0] [1] for this for my Linux distribution (which is the build from source variety) to avoid issues with upstream going away, or worse changing the contents of a file. Many different caches can be used, in case one is down as well. Simple example download script at [2]. [0] http://hashcache.rkeene.org/ http://hashcache.rkeene.org/ [1] https://chiselapp.com/user/rkeene/repository/hashcache/ https://chiselapp.com/user/rkeene/repository/hashcache/ [2] https://kitcreator.rkeene.org/fossil/artifact/d546c4b48dfce807 https://kitcreator.rkeene.org/fossil/artifact/d546c4b48dfce8...