Hi Ben, On 23 June 2017 at 15:20, Ben Coman <[email protected]> wrote:
> Typically Monticello mcz files are hosted on services shared via HTTP that > you can download with wget or curl, e.g.... > http://smalltalkhub.com/mc/Pharo/Pharo60/main > I guess if you pre-seed the package-cache, Pharo won't try to go to the > network to find the package. > That looks really promising, thanks for the link! I suppose that in the simplest case I would simply download every mcz file into the package cache and then I should be able to load any package without going over the network? Then the more sophisticated step would be to understand the dependency relationships so that I know what subset of the packages I need to install a given package e.g. Moose depends on Roassal depends on Trachel, etc. Is there an easy way to dump this dependency relationship e.g. to a text file? Is there also an easy way to determine the complete set of mcz files in the relevant universe? (The link above only covers projects hosted on SmalltalkHub, right? So I need to also know where to find all the potentially referenced projects on Github, etc, too?)
