----- "Stéphane Ducasse" <[email protected]> wrote:
| 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. Metacello 1.0-beta.25 will have a couple of new features that support the creation and use of historical/secondary repositories. I have added #fetch/#fetch: that downloads all of the packages/configurations into a target repository ... the using #repositoryOverrides: you can arrange that all of the package loads will done from the target repository (regardless of what the config specifies)... Dale _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
