Please note that we started discussing this topic a week ago. Maybe not everybody has read it (or remembers it). We started a wiki page [1] to keep track of possible solutions. Please also update that page so that we can keep track of the pros and cons of each solution. If somebody has time, it would be interesting to test out Metacello to see how well it would work for our needs. I think it could be a good match. Cheers, Adrian [1] http://code.google.com/p/pharo/wiki/PackageManagementSystem On Aug 20, 2009, at 21:13 , csrabak@bol.com.br wrote:
Em 20/08/2009 14:52, Damien Cassou < damien.cassou@gmail.com > escreveu:
On Thu, Aug 20, 2009 at 10:32 AM, Stéphane Ducasse 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.
If the Installer approach is akin the "Software Updates" we've in Pharo beta, I think some functionality has to put in place to work in a similar way Monticello or Universe where one can read the comments on the changes of package to upload.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project