2010/8/15 Guillermo Polito <[email protected]> > Thinking aloud, and maybe saying something useless because the work may > have started yet :P : > > Have you tought about something like > > - only one metacello config repository > - ConfigOf understanding messages like #loadForPharoVersion: '1.0' or > #loadInPharo10 or maybe just #load and request the pharo version to some > object in the image? > > > 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 > On Fri, Aug 13, 2010 at 5:26 PM, Stéphane Ducasse < > [email protected]> wrote: > >> unfortunately we spent all the student money for this year. >> >> Stef >> >> On Aug 13, 2010, at 5:33 PM, Miguel Enrique Cobá Martínez wrote: >> >> > I like the idea, but it requires a lot of effort in building the tool, >> > that does that. Maybe INRIA could sponsor some student hours just to >> > build this tool so that is ready for the 1.2 release. >> >> >> _______________________________________________ >> 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 >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
