esteban excellent!!! Now how can we load code for Pharo1.0 which is different for Pharo1.1 and soon Pharo1.2.... you see what I mean.
Ideally I would like to have the MetacelloRepository structured in a tree with versions 1.0/1.2.... so that in three years from now I can still load a version of something. The idea that we discuss with Dale is to be able to to a freeze of a configuration so that it copies all the dependent packages in a metacelloRepository. Stef > ConfigurationOfGoferProjectLoader project lastVersion load. > > With this... you'll never need again to perform once and again this > repetitive configuration... instead, you can do things like: > > Gofer project > load: 'Seaside30'; > load: 'Pier2'. > > You can see the full documentation here: > http://www.smallworks.com.ar/en/community/GoferProjectLoader > > Now I'm working on the promised page for configurations (Adrian: I really > sorry for the delay... I know I promised this a lot of time ago... but time > is the tyrant :( ) > > Cheers, > Esteban > > > > _______________________________________________ > 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
