[ANN] Pharo Metacello Universes
Locked
12
12
Re: [ANN] Pharo Metacello Universes
 
|
2010/8/15 Guillermo Polito <[hidden email]> Thinking aloud, and maybe saying something useless because the work may have started yet :P : Because with this approach there are still missing features we want: 1) Easily browse the available confs for a particular pharo version....how you do this? ok...maybe you can ask if the clkass undrestands #loadInPharo10 but it is more complicadte...Having different repos, we can just use the normal Monticello browser 2) We want to be self contained. Not only ConfOf packages, but also all packages should be backuped. You take an snapshot of the Conf and ALL the packages it uses. WIth this you are sure that in 10 years they will be able to laod it again. No problem if the owner removes packages from te repo or similar Cheers Mariano
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: [ANN] Pharo Metacello Universes
|
|
In reply to this post by Stéphane Ducasse
Stef,
Can we arrange to have a discussion about this issue at ESUG? There are a number of closely related things that need to be considered and I think that with email it is not easy ... Dale Stéphane Ducasse wrote: > 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 >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: [ANN] Pharo Metacello Universes
|
|
yes this will be much more efficient with a black board
stef On Aug 17, 2010, at 12:25 AM, Dale Henrichs wrote: > Stef, > > Can we arrange to have a discussion about this issue at ESUG? There are a number of closely related things that need to be considered and I think that with email it is not easy ... > > Dale > > Stéphane Ducasse wrote: >> 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 >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |