On Thu, Aug 20, 2009 at 10:32 AM, Stéphane
Ducasse<[email protected]> wrote:
> About http://code.google.com/p/pharo/wiki/PackagesTestedInPharo
> I was wondering if it would not be better to use the Universe mechanism.
> We could create a Pharo Universe and people could describe that their
> packages load in Pharo1.0
> This would be great and important to get a update to date catalog of
> what is working in Pharo1.0.
> What do you think?
For a simple solution, I would propose to provide a class with Pharo
to contain a script per method, each script installing a package,
i.e., like we currently do in ScriptLoader but in another class. This
is similar to what Keith's Packages support already, but without the
Sake syntax and implementation that nobody looked at as of now.
A method could look like:
omnibrowser
self installer lukas
project: 'omnibrowser';
install: 'OmniBrowser';
install: 'OB-Standard';
install: 'OB-Morphic';
install: 'OB-SUnitIntegration'.
The installer used could be either Installer or something else.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
