this was more or less what I had in mind but with a limited knowledge of metacello. Stef
I think that we should do is a piece of code that does the following:
- Take a ConfiguraitonOfXXX and do a "publish in Pharo Repository" - This can propmt which Pharo version, or directly which PharoRepository - Then it will ask which VERSION should be loaded in the already selected Pharo version - It should be asked WHICH group (optional)
Once this is done, the code has to do the following:
- Iterates all the project and packages referenced and COPY ALL OF THEM into the same repository. Or maybe we can have another repo. This will copy all the .mzc of the project and its dependencies. With this you will make sure that you have EVERYTHING you need to load it.
- take that ConfigurationOfXXX and automatically compile a class side #load that based in your answers, does the correct job. In addition, this method should do a repositoryOverride: with the selected repository. Example:
load | version | version := self project version: selectedVersion. version repositoryOverrides: selectedPharoRepository. version load: selectedGroup.
Maybe it can implement a particular load: that recieves the common parameter
Then, if you are in Pharo 1.0 the only thing you have to do is to explore the repository PharoRepository10 and browse the confs....you select the one you want and load it (with Gofer or Monticello Browser). Once that is done, you just evaluate:
ConfiguarationOfXXX load.
and that's all.
What do you think ? Dale?
Cheers
-- 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