2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
That does work.
You see ? It was a matter of the version, no more than that. Now you have your PharoWeb image :)
As with the Loader solution, it prompts for the user name and password; other solutions available trap those and provide reasonable defaults, which is nice for automated builds.
Yes true. However, maybe other people rather to put a real username and password. I think this is more flexible. It would be cool to hear opinions.
------------------------------ *From:* pharo-project-bounces@lists.gforge.inria.fr [mailto: pharo-project-bounces@lists.gforge.inria.fr] *On Behalf Of *Mariano Martinez Peck *Sent:* Saturday, January 09, 2010 7:34 PM
*To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
Mariano,
Whether it makes sense or not, try it yourself. Either Loader is more than you think it is, or it does something that is critical to allowing Metacello to succeed.
Can you try this and tell me if it works:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
((Smalltalk at: #ConfigurationOfSeaside28) project version: '2.8.4.2') load
Bill
------------------------------ *From:* pharo-project-bounces@lists.gforge.inria.fr [mailto: pharo-project-bounces@lists.gforge.inria.fr] *On Behalf Of *Mariano Martinez Peck *Sent:* Saturday, January 09, 2010 6:37 PM
*To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/10 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
Hi Bill,
this one works for me with the current pharo core 1.0 rc1, update upto 10505
"execute this:" Gofer new squeaksource: 'Loader'; package: 'Loader'; load. "then this" Loader new load: 'Pharo' version: '1.0-rc2.10505'. "then this" Loader new load: 'Seaside28' version: '2.8.4.2'
The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot of additional pharo packages. I guess you won't need that just to get seaside working.
But isn't the loader alpha yet?
Maybe even before. Hoever, it does not make sense. Loader is just a simplifier API to metacello. If Loader works with Seaside2.8, ConfigurationOfSeaside28 MUST work too.
I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello.
Yes, please. Let's try to use this tools first. When we are stable enough we start with another ones.
Cheers
Mariano
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ 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
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project