On Jan 28, 2013, at 9:29 PM, Dale Henrichs wrote: > Metacello does use the package cache, but there _are_ certain specifications > that can force a load from the repository: > > 1) If a configuration is blessed as #development, the configuration will be > downloaded from the repository when referenced (to ensure that you are > picking up the latest configuration > > 2) If you have a "naked" package in a specification (i.e/, no file: > specified), then Metacello will _ALWAYS_ access the repository to load the > LATEST mcz file...most often this is triggered when you load a baseline > version (where no file: are specified). > > Moose tends to reference baselines in this manner to ensure that the latest > packages are loaded. This is the most likely cause of your "problem". > > If you've specified a file: and Metacello finds the file in the package-cache > it does not hit the repository to download the file.
Thanks for the explanation. I'm happy because I found my bug (in fact you found my bug :). And there is a lesson. Do not code when you are too tired. Dale. > Dale > > ----- Original Message ----- > | From: "Stéphane Ducasse" <[email protected]> > | To: "Pharo Development" <[email protected]> > | Sent: Monday, January 28, 2013 7:05:16 AM > | Subject: [Pharo-project] How to force Metacello to use the package cache? > | > | Hi guys > | > | I'm trying to work on Moose and I get 200 package to download during > | my experiments ~ 30 min at minimum > | Does anybody have an idea how to make sure metacello use the package > | cache? > | > | I started to comment > | > | cacheGofer > | > | cacheGofer == nil > | ifTrue: [ > | "don't use a caching Gofer here, since we expect the > contents to > | change during a fetch operation" > | cacheGofer := Gofer new. > | >>>> cacheGofer disablePackageCache. > | cacheGofer repository: self cacheRepository. ]. > | ^ cacheGofer > | > | But no success so far. > | > | Still looking around > | Stef > | >
