how can I tag a symbolic..

Dale

how can I say that a development symbolic version should load the latest version?
Right now I have

development: spec
        <symbolicVersion: #'development'>

        spec for: #'pharo1.4.x' version: '1.3'.


but I have to update it.

Stef

I usually use a baseline instead of the actual version for
development. This is what you want most of the time, and it changes
much less often.

Cheers,
Doru


On Thu, Mar 15, 2012 at 9:04 AM, stephane ducasse
<[hidden email]> wrote:


--
www.tudorgirba.com

"Every thing has its own flow"

> I usually use a baseline instead of the actual version for
> development. This is what you want most of the time, and it changes
> much less often.

With MetacelloBrowser and Versionner, generating a new version takes one click and another to accept the version comment.

Alexandre


--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Stef,

It depends upon what you mean by "latest version".

If you mean "latest versions of all packages" then Doru's suggestion of using a baseline version there applies.

If you mean literally `ConfigurationOfXXX project latestVersion`, there _is_ a way to do that, but I'm not sure that that is what you want.

If you mean "always download the latest version of the ConfigurationOfXXX mcz file and then load version 1.3", then that happens if you change the blessing in the version spec for 1.3 to #development:

version13:spec
<version: '1.3' imports: .....>

  spec for: #common do: [
    spec blessing: #development.
....
  [.

Dale

----- Original Message -----
| From: "stephane ducasse" <[hidden email]>
| To: [hidden email]
| Sent: Thursday, March 15, 2012 1:04:09 AM
| Subject: [Metacello] how can I tag a symbolic..
|
| Dale
|
| how can I say that a development symbolic version should load the
| latest version?
| Right now I have
|
| development: spec
| <symbolicVersion: #'development'>
|
| spec for: #'pharo1.4.x' version: '1.3'.
|
|
| but I have to update it.
|
| Stef

The assumption with `blessing: #development` declaration (the one I recommend) is that over time the definition of 1.3 will change as bugs are fixed and once Pharo1.4 itself stabilizes, you will be able to finalize the definition of 1.3 ...

Dale

----- Original Message -----
| From: "Dale Henrichs" <[hidden email]>
| To: [hidden email]
| Sent: Thursday, March 15, 2012 12:06:57 PM
| Subject: Re: [Metacello] how can I tag a symbolic..
|
| Stef,
|
| It depends upon what you mean by "latest version".
|
| If you mean "latest versions of all packages" then Doru's suggestion
| of using a baseline version there applies.
|
| If you mean literally `ConfigurationOfXXX project latestVersion`,
| there _is_ a way to do that, but I'm not sure that that is what you
| want.
|
| If you mean "always download the latest version of the
| ConfigurationOfXXX mcz file and then load version 1.3", then that
| happens if you change the blessing in the version spec for 1.3 to
| #development:
|
| version13:spec
| <version: '1.3' imports: .....>
|
|   spec for: #common do: [
|     spec blessing: #development.
| ....
|   [.
|
| Dale
|
| ----- Original Message -----
| | From: "stephane ducasse" <[hidden email]>
| | To: [hidden email]
| | Sent: Thursday, March 15, 2012 1:04:09 AM
| | Subject: [Metacello] how can I tag a symbolic..
| |
| | Dale
| |
| | how can I say that a development symbolic version should load the
| | latest version?
| | Right now I have
| |
| | development: spec
| | <symbolicVersion: #'development'>
| |
| | spec for: #'pharo1.4.x' version: '1.3'.
| |
| |
| | but I have to update it.
| |
| | Stef
|

On Mar 15, 2012, at 8:09 PM, Dale Henrichs wrote:

> The assumption with `blessing: #development` declaration (the one I recommend) is that over time the definition of 1.3 will change as bugs are fixed and once Pharo1.4 itself stabilizes, you will be able to finalize the definition of 1.3 ...


I was wondering how I specify a symbolic version as development without having to mention version

 development: spec
  <symbolicVersion: #'development'>
 
  spec for: #'pharo1.4.x' version: '1.3'.
                                                        ^^^^^
                                                        here :)

Because I could want to say for 1.3
        spec for: #'pharo1.3.x' version: '0.9.
        but for
        spec for: #'pharo1.4.x' version: #development??.
       
Stef

I'm not sure I understand ... which version do you want to get loaded when you specify #development?

Dale

----- Original Message -----
| From: "stephane ducasse" <[hidden email]>
| To: [hidden email]
| Sent: Thursday, March 15, 2012 2:43:06 PM
| Subject: Re: [Metacello] how can I tag a symbolic..
|
|
| On Mar 15, 2012, at 8:09 PM, Dale Henrichs wrote:
|
| > The assumption with `blessing: #development` declaration (the one I
| > recommend) is that over time the definition of 1.3 will change as
| > bugs are fixed and once Pharo1.4 itself stabilizes, you will be
| > able to finalize the definition of 1.3 ...
|
|
| I was wondering how I specify a symbolic version as development
| without having to mention version
|
|  development: spec
|   <symbolicVersion: #'development'>
|  
|   spec for: #'pharo1.4.x' version: '1.3'.
| ^^^^^
| here :)
|
| Because I could want to say for 1.3
| spec for: #'pharo1.3.x' version: '0.9.
| but for
| spec for: #'pharo1.4.x' version: #development??.
|
| Stef
|
|

On Mar 16, 2012, at 2:51 AM, Dale Henrichs wrote:

> I'm not sure I understand ... which version do you want to get loaded when you specify #development?

The latest one.

`ConfigurationOfXXX project latestVersion`?

----- Original Message -----
| From: "stephane ducasse" <[hidden email]>
| To: [hidden email]
| Sent: Friday, March 16, 2012 4:03:42 AM
| Subject: Re: [Metacello] how can I tag a symbolic..
|
|
| On Mar 16, 2012, at 2:51 AM, Dale Henrichs wrote:
|
| > I'm not sure I understand ... which version do you want to get
| > loaded when you specify #development?
|
| The latest one.
|
|
| >
| > Dale
| >
| > ----- Original Message -----
| > | From: "stephane ducasse" <[hidden email]>
| > | To: [hidden email]
| > | Sent: Thursday, March 15, 2012 2:43:06 PM
| > | Subject: Re: [Metacello] how can I tag a symbolic..
| > |
| > |
| > | On Mar 15, 2012, at 8:09 PM, Dale Henrichs wrote:
| > |
| > | > The assumption with `blessing: #development` declaration (the
| > | > one I
| > | > recommend) is that over time the definition of 1.3 will change
| > | > as
| > | > bugs are fixed and once Pharo1.4 itself stabilizes, you will be
| > | > able to finalize the definition of 1.3 ...
| > |
| > |
| > | I was wondering how I specify a symbolic version as development
| > | without having to mention version
| > |
| > |  development: spec
| > |   <symbolicVersion: #'development'>
| > |  
| > |   spec for: #'pharo1.4.x' version: '1.3'.
| > | ^^^^^
| > | here :)
| > |
| > | Because I could want to say for 1.3
| > | spec for: #'pharo1.3.x' version: '0.9.
| > | but for
| > | spec for: #'pharo1.4.x' version: #development??.
| > |
| > | Stef
| > |
| > |
|
|

On Mar 16, 2012, at 5:02 PM, Dale Henrichs wrote:

> `ConfigurationOfXXX project latestVersion`?

My reasoning is the following.
        We have symbolic version
                for stable we give a version and we are happy
                for development we can give a version but this is important to also know how to say for development symbolic version take the latest
        so this is why I asked is there a way to express using the symbolic mechanism that a dev is just loading the latest.

Stef

I'm double and triple checking because we have left the realm of "declarative specification":)

To define a symbolic version that uses the 'latestVersion' add a method like the following to your configuration:

  development
        "method name isn't important ... the pragma is the important piece.
         Method should return a version string"

        <defaultSymbolicVersion: #development>
       
        ^self project latestVersion versionString

This means you can use any sort of wild algorithmic calculation for the symbolic version.

Make sure you are using this style of project definition:

project
    ^ project
        ifNil: [
            "Bootstrap Metacello if it is not already loaded"
            self class ensureMetacello.
            project := MetacelloMCProject new projectAttributes: self customProjectAttributes. "Create the Metacello project"
            (Smalltalk at: #'MetacelloVersionConstructor') on: self project: project. "Construct the project"
            project loadType: #'linear'. "change to #atomic if desired"
            project ]

with a customeAttributes method:

customProjectAttributes
    ^ #()


----- Original Message -----
| From: "stephane ducasse" <[hidden email]>
| To: [hidden email]
| Sent: Friday, March 16, 2012 11:17:11 AM
| Subject: Re: [Metacello] how can I tag a symbolic..
|
|
| On Mar 16, 2012, at 5:02 PM, Dale Henrichs wrote:
|
| > `ConfigurationOfXXX project latestVersion`?
|
| My reasoning is the following.
| We have symbolic version
| for stable we give a version and we are happy
| for development we can give a version but this is important to also
| know how to say for development symbolic version take the latest
| so this is why I asked is there a way to express using the symbolic
| mechanism that a dev is just loading the latest.
|
| Stef
| >
| > ----- Original Message -----
| > | From: "stephane ducasse" <[hidden email]>
| > | To: [hidden email]
| > | Sent: Friday, March 16, 2012 4:03:42 AM
| > | Subject: Re: [Metacello] how can I tag a symbolic..
| > |
| > |
| > | On Mar 16, 2012, at 2:51 AM, Dale Henrichs wrote:
| > |
| > | > I'm not sure I understand ... which version do you want to get
| > | > loaded when you specify #development?
| > |
| > | The latest one.
| > |
| > |
| > | >
| > | > Dale
| > | >
| > | > ----- Original Message -----
| > | > | From: "stephane ducasse" <[hidden email]>
| > | > | To: [hidden email]
| > | > | Sent: Thursday, March 15, 2012 2:43:06 PM
| > | > | Subject: Re: [Metacello] how can I tag a symbolic..
| > | > |
| > | > |
| > | > | On Mar 15, 2012, at 8:09 PM, Dale Henrichs wrote:
| > | > |
| > | > | > The assumption with `blessing: #development` declaration
| > | > | > (the
| > | > | > one I
| > | > | > recommend) is that over time the definition of 1.3 will
| > | > | > change
| > | > | > as
| > | > | > bugs are fixed and once Pharo1.4 itself stabilizes, you
| > | > | > will be
| > | > | > able to finalize the definition of 1.3 ...
| > | > |
| > | > |
| > | > | I was wondering how I specify a symbolic version as
| > | > | development
| > | > | without having to mention version
| > | > |
| > | > |  development: spec
| > | > |   <symbolicVersion: #'development'>
| > | > |  
| > | > |   spec for: #'pharo1.4.x' version: '1.3'.
| > | > | ^^^^^
| > | > | here :)
| > | > |
| > | > | Because I could want to say for 1.3
| > | > | spec for: #'pharo1.3.x' version: '0.9.
| > | > | but for
| > | > | spec for: #'pharo1.4.x' version: #development??.
| > | > |
| > | > | Stef
| > | > |
| > | > |
| > |
| > |
|
|