Luke Gorrie wrote
Hi Paul,
On 23 June 2017 at 22:11, Paul DeBruicker <
pdebruic@
> wrote:
For those projects described with Metacello baselines or configurations you can issue a #fetch command to download all the Monticello packages needed to load the projects into your image....
Thanks for this idea!
Could be that a "high-brow" approach based on Metacello metadata is an interesting alternative to a "low-brow" approach based on simply scraping the package-cache/ directory after installation.
Here is what I would really like (restating from another mail):
To make a dump of all available packages (restricting to ones with Metacello configurations is probably fine) and, for each package, to make a list of:
- The mcz files required for installation (and any other downloded resources if there are some...?) - The sha256 hash of each mcz file (assume I can get this easily if the file is downloaded) - The URL where the file was downloaded from / should be downloaded from in the future
Do you think this can be determined in a straightforward way from Metacello metadata?
Hi Luke, I think it is straight forward, if not already supported. I think you want data that is contained in the instance of the MetacelloVersionLoadDirective that is created by Metacello's record command (https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloScri...). But I'm not sure where to look to give you the URL from where its loading the package. So continuing with the Seaside example I posted replace the #fetch with a #record and inspect the output of the command. Hope this helps Paul. -- View this message in context: http://forum.world.st/Recursively-downloading-Pharo-packages-Building-images... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.