[Pharo-project] Which ConfigurationOfPharo should use in Pharo 1.2 ?
I tried the 2 latest Beta and fail, also the 1.1 version fail. Which ConfigurationOfPharo I should use with Pharo 1.2 ? Cheers.
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@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.
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@gmail.com<mailto:garduino@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.
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@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@gmail.com <mailto:garduino@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.
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@vmware.com<mailto:dhenrich@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@gmail.com<mailto:garduino@gmail.com><mailto:garduino@gmail.com<mailto:garduino@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.
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@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@vmware.com<mailto:dhenrich@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@gmail.com<mailto:garduino@gmail.com><mailto:garduino@gmail.com<mailto:garduino@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 =================================================
Sorry I should have written: "Marcus", sorry. 2011/2/4 Germán Arduino <garduino@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@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@vmware.com<mailto:dhenrich@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@gmail.com<mailto:garduino@gmail.com><mailto:garduino@gmail.com<mailto:garduino@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 =================================================
On Feb 4, 2011, at 6:01 AM, Guillermo Polito wrote:
Should we remove invalid and unused versions?
Good question. I think the first rule of thumb is to never remove a version from a configuration. Once you have published a configuration you don't know if someone else has referenced a published version in their configuration and if you remove the version you will break their configuration. Removing a configuration version is the moral equivalent of deleting an mcz file from a repository...it only hurts the other folks that depend upon the file. Sooo, it follows that a) if you don't think any is using the version and b) you don't mind if you break someone else's configuration then you can go ahead and remove the version...in the case of an emergency, the removed version can be restored from and older version of the configuration mcz file ... Dale
participants (3)
-
Dale Henrichs -
Germán Arduino -
Guillermo Polito