I'm hoping something like metacello in our process makes these things go away ;-)
can you retrospectively edit the update to point to the exact version? Mike On Monday, October 5, 2009, Lukas Renggli <[email protected]> wrote: >> argh >> lukas changed the gofer interface. > > I had to do this, because people have different naming conventions for > packages. Before Gofer worked either for Moose or Seaside, but not > for both at the same time. To solve the problem you have to follow the > advice in the debugger. You tell Gofer if you specify an exact version > (#addVersion:) or a package name (#addPackage:). If you don't do that > (by proceeding or using #addPrefix:) the result is pretty much > undefined. See the Moose mailing list for a lengthy discussion. > >> We should hardcode the number... >> It was working before. > > For obvious reasons users of Gofer should always use a fixed version, > not the "latest" one. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
