Damien, SqueakMap appears to be absent from that list - I had missed that. I just took another run at it, bypassing the one-click image, and the package loader was happier. Update the list from the net, and it seems to work. Shout complained about dependencies, but since it is on the list, I am not too worried. My existing image serves, but I am eager to build a new one when appropriate.
Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: [EMAIL PROTECTED] Tel: (352) 273-6785 FAX: (352) 392-7029 >>> [EMAIL PROTECTED] 12/03/08 4:12 AM >>> On Wed, Dec 3, 2008 at 7:24 AM, Bill Schwab <[EMAIL PROTECTED]> wrote: > As Pharo 1.0 takes shape, what is the plan for getting packages loaded > the way each of us wants? Is Installer the preferred route? Would I be > expected to script it (I find myself hoping so - load the latest of > this, that, specific version of this other thing, etc.)? I tried to > quickly load Shout and the SM package loader was not happy, but that > could easily be my fault. > > More questions and comments, but first, I need to get some overdue > sleep. The tools referenced at http://code.google.com/p/pharo/wiki/Packages will be included by default (this includes Shout, eCompletion, OB...). Installer and Universe will probably be both available to install other things. -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ 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
