Hi Hilaire, Which Pharo version? Have you found any solution to this? In Gofer there was #disablePackageCache, in Metacello I don't know, maybe experimenting with MetacelloLoaderPolicy but there are no class comments. Cheers, Hernán 2017-12-18 17:24 GMT-03:00 Hilaire <hilaire@drgeo.eu>:
If understood correctly, when using a tonel file repository to build up an image, Pharo seems instead to take the sources from some package-cache, which is out of sync, because the tonel file repo was updated from another image, with a different cache. I guess I can trick the file system but it is for the least very annoying, for the worst unreliable.
Le 10/12/2017 à 18:16, Hilaire a écrit :
I am using tonel format to install from and save to a local repository.
How to prevent Monticello/Configuration/Metacello to save packages to the image package-cache dir?
Even when installing from a configuration with repo on tonel file format, packages get created in the image package-cache directory.
I have read there and there, Pharo gets confused and uses wrongly the package-cache versions and not the local repo.
-- Dr. Geo http://drgeo.eu