Yeah, I explained the reason previously. You have to tell Gofer if this is a version or package specification. In the beginning I though that Gofer can guess if the stupd string is a version or just a package name, but then I run into all those wired non-standard naming of packages that makes this impossible. Lukas On 19 March 2010 20:38, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
thanks!
On Mar 19, 2010, at 7:05 PM, Miguel Enrique Cobá Martinez wrote:
El vie, 19-03-2010 a las 18:55 +0100, Stéphane Ducasse escribió:
HI lukas
   Gofer new        squeaksource: 'Rio'; package: 'Rio-Kernel-razavi_acm_org.89'; package: 'Rio-Grande-kph.45'; load.
   does not work while the following does and load the same files.
   Gofer new        squeaksource: 'Rio'; package: 'Rio-Kernel'; package: 'Rio-Grande'; load.
what is the mistake I'm doing?
The lateste versions of Gofer use package to specify a package name without version. It takes the greatest version number. To get a given version you use the version: (http://www.lukas-renggli.ch/blog/gofer) method in the current gofer like: Gofer new   squeaksource: 'KomHttpServer';   version: 'DynamicBindings-gc.7';   version: 'KomServices-gc.19';   version: 'KomHttpServer-gc.32';   update.
The previous versions took the package and number and install that specific version. This works no more.
Cheers
Stef _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch