No, Gofer doesn't look in repositories you don't specify. However, it uses and prefers your local package-cache if it contains a newer version of your package (which is likely the case in your example). You can disable the package-cache by sending something like #disablePackageCache to your Gofer instance (I don't have an image at hand right now, but you find it in the code and documentation). Gofer is part of Pharo and not maintained in my repository anymore. This #update method should be removed it is not supposed to work anymore. Lukas On Sunday, 9 January 2011, Hernán Morales Durand <hernan.morales@gmail.com> wrote:
Hi list, I have some issues with Gofer, maybe already known. When I evaluate:
Gofer new     squeaksource: 'Subjectivity';     package: 'Subjectivity';     load.
it seems that Gofer takes the first package named Subjectivity it founds which in this case is http://www.squeaksource.com/Decisionstrategy.html while I wanted to take it from http://www.squeaksource.com/Subjectivity.html (please see the screenshot). After then I've tried to update "Gofer upgrade" for a fix, but it seems it cannot connect to http://source.lukas-renggli.ch and then entered in an endless loop. Any hint? (Using Pharo1.2beta Latest update: #12294)
Cheers,
-- Hernán Morales Information Technology Manager, Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.
-- Lukas Renggli www.lukas-renggli.ch