Similar to #324, the dependencies are currently downloaded from hard coded upstream URLs, which defeats documentation and maintenance in general and using alternative sources in particular (e.g. a custom version).
Instead, we should facilitate the common local cache based pattern similar to Maven/Gem/Pip/etc., i.e. dependency download and usage are separate steps during the build, which simplifies/unifies subsequent build steps and saves bandwidth/time on the side - as such this details #293.
Similar to #324, the dependencies are currently downloaded from hard coded upstream URLs, which defeats documentation and maintenance in general and using alternative sources in particular (e.g. a custom version).
Instead, we should facilitate the common local cache based pattern similar to Maven/Gem/Pip/etc., i.e. dependency download and usage are separate steps during the build, which simplifies/unifies subsequent build steps and saves bandwidth/time on the side - as such this details #293.