I'm trying out a trick with extending Installer to always try load from package-cache. Perhaps Gofer can be similarly tweaked?
(I did it by making Installer use an MCRepositoryGroup, which iterates over its contained repositories... and tries the package-cache first.) frank On 28 January 2013 18:02, Stéphane Ducasse <[email protected]> wrote: > for me it systematically loads everyghing so I'm trying to nuke it in gofer > kind of I put the enable code in the disable method :) and I will see. > > > > disablePackageCache > "Disable the use of the package-cache repository." > > packageCacheRepository := MCCacheRepository default > > > > > Stef > > On Jan 28, 2013, at 12:21 PM, Sven Van Caekenberghe wrote: > >> >> On 28 Jan 2013, at 16:05, Stéphane Ducasse <[email protected]> wrote: >> >>> 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? >> >> In my experience, Metacello/Monticello caching *is* used (provided you keep >> using the same package-cache directory). >> If you open the Transcript while loading and/or inspect the Metacello >> loading result, you'll see when the cache is being used. >> >> IMHO, the downloading is not the worst part, it is more the >> loading/compiling - probably due to massive notifications and the reactions >> on that, it is hard to analyse and I am no expert at all. >> >>> 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 >>> >>> >> >> > >
