Whatever you guys want, so long as it indeed works. With the explicit version, ConfigurationOfSeaside28 seems to do the trick. I suggest adding a link to the downloads page with code for FFI and Seaside for starters.
Another idea would be to add class methods to Gofer that use Metacello. The existing #seaside28 should be rewritten or removed. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Miguel Enrique Cobá Martinez Sent: Saturday, January 09, 2010 7:45 PM To: [email protected] Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 El sáb, 09-01-2010 a las 18:58 -0500, Schwab,Wilhelm K escribió: > Miguel, > > My concern is over testing of the RC images. Whether Loader is alpha or not > seems a little less important than providing what people will need in order > to test. As a friend of mine would say, "don't make it hard on people to > help you." > > I will gladly download a web image, run something in production, or run an > alpha installer. The important thing is to have a clear message and a > working solution to the problem. > > Bill Yes, but Loader hasn't been announced yet. That is the point. Lets concentrate in Gofer/Metacello that is the _blessed_ way to install in Pharo 1.0 Cheers > > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Miguel Enrique Cobá Martinez > Sent: Saturday, January 09, 2010 6:21 PM > To: [email protected] > Subject: Re: [Pharo-project] [BetaTesting] [ANN] > Pharo1.0-10505-rc1dev10.01.1 > > 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? > > 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. > > Cheers > > -- > Miguel Cobá > http://miguel.leugim.com.mx > > > _______________________________________________ > 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 -- Miguel Cobá http://miguel.leugim.com.mx _______________________________________________ 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
