[Pharo-project] Which ConfigurationOfPharo should use in Pharo 1.2 ?

Marcus Denker marcus.denker at inria.fr
Sat Feb 5 08:31:13 CET 2011


On Feb 5, 2011, at 12:16 AM, Germán Arduino wrote:

> Sorry I should have written: "Marcus", sorry.
> 

I attach the complete script used for building 1.2 as the builder.sh stiches it together:


-------------- next part --------------
A non-text attachment was scrubbed...
Name: Pharo-1.2.st
Type: application/octet-stream
Size: 972 bytes
Desc: not available
URL: <http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20110205/afe6212f/attachment.obj>
-------------- next part --------------



> 2011/2/4 Germán Arduino <garduino at gmail.com>:
>> Thanks by the explanations Dale.
>> 
>> Thanks Guillermo and Markus by the points.
>> 
>> Until moment any way of installation I tried failed with different
>> sort of messages.
>> 
>> By now I downloaded the ready image pointed by Markus but would like
>> to build my own.
>> 
>> Thanks!
>> 
>> 
>> 2011/2/4 Dale Henrichs <dhenrich at vmware.com>:
>>> Sure:
>>> 
>>>  http://gemstonesoup.wordpress.com/2011/01/17/metacello-1-0-beta-28-unearthed/
>>> 
>>> Be sure to look at the section of development cycle ... and tools support, too...
>>> 
>>> Dale
>>> 
>>> On Feb 4, 2011, at 6:37 AM, Guillermo Polito wrote:
>>> 
>>> Dale, Is there a place where I can read how to configure the symbolic versions?
>>> 
>>> Thx!
>>> Guille :)
>>> 
>>> On Fri, Feb 4, 2011 at 11:29 AM, Dale Henrichs <dhenrich at vmware.com<mailto:dhenrich at vmware.com>> wrote:
>>> ConfigurationOfPharo should have a #stable symbolic version defined that specifies the version that should be used in 1.2, 1.1, and 1.0 ... then one just loads the #stable version:
>>> 
>>>  (ConfigurationOfPharo project version: #stable) load
>>> 
>>> and you'll get the right version loaded for the platform version ... even though the version is under development I think it is valid to specify a #stable symbolic version for Pharo1.2, just so folks don't have to ask this question over and over again ... Don't let the name 'stable' scare you ...
>>> 
>>> The intent is that the #stable symbolic version specifies the version that should be loaded .... the developer decides which versions are #stable for each platform version and when a new version becomes "the version to use" the developer updates the specification.
>>> 
>>> The users of a configuration shouldn't have to think ... remember in the past the recommended pattern was:
>>> 
>>>  ConfigurationOfPharo project latestVersion load
>>> 
>>> and that worked fine until Pharo1.1 and Pharo1.2 were introduced. The expression:
>>> 
>>>  (ConfigurationOfPharo project version: #stable) load
>>> 
>>> is intended to replace the use of #latestVersion because it makes it possible to explicitly specify the "latest version" on a platform by platform and platform version basis...
>>> 
>>> Sorry if I appear to be ranting ... I'm just trying to get the message out:)
>>> 
>>> Dale
>>> 
>>> On Feb 4, 2011, at 6:01 AM, Guillermo Polito wrote:
>>> 
>>> I'm Using '1.2-beta2'.
>>> 
>>> Should we remove invalid and unused versions?  I'll add a few comments at lunch time ;)
>>> 
>>> On Fri, Feb 4, 2011 at 10:53 AM, Germán Arduino <garduino at gmail.com<mailto:garduino at gmail.com><mailto:garduino at gmail.com<mailto:garduino at gmail.com>>> wrote:
>>> I tried the 2 latest Beta and fail, also the 1.1 version fail.
>>> 
>>> Which ConfigurationOfPharo I should use with Pharo 1.2 ?
>>> 
>>> Cheers.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> --
>> =================================================
>> Germán S. Arduino  <gsa @ arsol.net>   Twitter: garduino
>> Arduino Software & Web Hosting   http://www.arduinosoftware.com
>> PasswordsPro  http://www.passwordspro.com
>> =================================================
>> 
> 

--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.



More information about the Pharo-project mailing list