>I was trying to load the latestVersion of ConfigurationOfSeaside3 into the >latest PharoCore 1.2
No, this wont work. The default config should be used only on Pharo-dev since it loads tests, tools, ... Loading Seaside on Pharo Core makes only sense for deployment and then you have to pick the pieces from the config that you need. You can do this with the #load: method on the config and given the groups you need: (ConfigurationOfSeaside30 project version: '3.0.3') load: { 'Grease Core' } for instance loads only Grease. >Is there a place to get the script that turns PharoCore 1.2 into >Pharo 1.2 ? Pharo 1.2 is always built by using (guess what, tadaaa): the "ConfigurationOfPharo" So from PharoCore 1.2 to PharoDev 1.2: ------------------------------------------------------------------- Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) load ------------------------------------------------------------------- The last version is currently "1.2-beta2", just look into the ConfigurationOfPharo class. The build script "Pharo-1.2.st" that the Hudson server is using is available at: http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20110203/8c0e4bd2/attachment.obj It first updates the core and does some other "magic". You can just file this into a recent 1.2 core and your machine is the build server :) Take care when you use it - it automatically saves when finished and therefore overwrites the core image used. Bye T -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de |
Thanks a lot, again, Torsten, I will be checking this out over the weekend.
Your replies are really helpful and clear. Sven BTW: a big thanks to all the others involved in making all this possible, I know it is a lot of hard work. On 04 Feb 2011, at 11:18, Torsten Bergmann wrote: >> I was trying to load the latestVersion of ConfigurationOfSeaside3 into the >latest PharoCore 1.2 > > No, this wont work. The default config should be used > only on Pharo-dev since it loads tests, tools, ... > > Loading Seaside on Pharo Core makes only sense for deployment > and then you have to pick the pieces from the config that > you need. You can do this with the #load: method on the > config and given the groups you need: > > (ConfigurationOfSeaside30 project version: '3.0.3') load: { 'Grease Core' } > > for instance loads only Grease. > >> Is there a place to get the script that turns PharoCore 1.2 into >> Pharo 1.2 ? > > Pharo 1.2 is always built by using (guess what, tadaaa): > the "ConfigurationOfPharo" > > > So from PharoCore 1.2 to PharoDev 1.2: > > ------------------------------------------------------------------- > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) load > ------------------------------------------------------------------- > > The last version is currently "1.2-beta2", just look into the > ConfigurationOfPharo class. > > > The build script "Pharo-1.2.st" that the Hudson server is using > is available at: > > http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20110203/8c0e4bd2/attachment.obj > > It first updates the core and does some other "magic". > > You can just file this into a recent 1.2 core and your machine is the > build server :) > > Take care when you use it - it automatically saves when finished and > therefore overwrites the core image used. > > Bye > T > > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de |
Free forum by Nabble | Edit this page |