[Best practices?] Build number in packaged image

My favorite solution was to put "Smalltalk at: #TheApplicationVersionString put: '1.2.7.0 v0' .false" in the base config map "Config. Expressions" field...followed by a "true" line. Then whenever a new map was opened, the version was updated and anyone loading the map would automatically get the correct version. (including the builder). BTW, the "true" line would have the associated required maps, (if any)...

Hope that helps

On Wed, Nov 28, 2012 at 3:24 PM, <a href="javascript:" target="_blank" gdf-obfuscated-mailto="yy_9N936O44J">jtu...@... <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="yy_9N936O44J">jtu...@...> wrote:

Hi,

Do others include some string into their packaged images to indicate the build number or - even better - the version name of some config map or such? How do they do that? 

Almost everything that I can think of has drawbacks, most of them being that some user has to actively do something that ends up in a newly compiled method (whereby the version number of a config map wouldn't be accurate any more unless you first version that stuff and package afterwards...).

Are there any best practices how to do that fully automatically in the packaging process? Where do you keep these numbers/strings? How do you update them?

Just wondering because this would be handy in some situations. Mostly ones that are unpleasant (like users reporting urgent errors friday nights).

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/l1oai8pChQsJ.
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="yy_9N936O44J">va-sma...@....
To unsubscribe from this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="yy_9N936O44J">va-smalltalk...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

It should, well, in my case it is attached to a config map version,... so somehow it is ;-)

Sebastian

Am 28.11.2012 13:13, schrieb <a href="javascript:" target="_blank" gdf-obfuscated-mailto="sg0g4juQHu4J">jtu...@...:

but that is not under version control, right?

Am Mittwoch, 28. November 2012 21:39:06 UTC+1 schrieb Sebastian Heidbrink:

I usually take the inheritedUserField

Sebastian


Am 28.11.2012 12:24, schrieb [hidden email]:
> Hi,
>
> Do others include some string into their packaged images to indicate
> the build number or - even better - the version name of some config
> map or such? How do they do that?
> Almost everything that I can think of has drawbacks, most of them
> being that some user has to actively do something that ends up in a
> newly compiled method (whereby the version number of a config map
> wouldn't be accurate any more unless you first version that stuff and
> package afterwards...).
>
> Are there any best practices how to do that fully automatically in the
> packaging process? Where do you keep these numbers/strings? How do you
> update them?
>
> Just wondering because this would be handy in some situations. Mostly
> ones that are unpleasant (like users reporting urgent errors friday
> nights).
>
> Joachim
> --
> You received this message because you are subscribed to the Google
> Groups "VA Smalltalk" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/va-smalltalk/-/l1oai8pChQsJ.
> To post to this group, send email to [hidden email].
> To unsubscribe from this group, send email to
> va-smalltalk...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/va-smalltalk?hl=en.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/0YXdhIVN1UgJ.
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="sg0g4juQHu4J">va-sma...@....
To unsubscribe from this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="sg0g4juQHu4J">va-smalltalk...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

I don't usually suffer from the "over-thinking it" problem...usually the opposite...  :o)  I think simply the config expressions are evaluated until one returns true and its associated required maps are loaded. So the false line just sets the version into a global using a string and continues on to the next line that loads the required maps, (and is "true"). We have it in the base map so it's guaranteed to be there, (with the pkging rule you mentioned). It was much simpler for us because we were okay with a string in the expression and didn't care to try and grab the map version it was loading or something like that...but that would be way cool if you can get that to work.

Usually I only get one of those adjectives...and it's not the "cool" one....   :o)

Hope that helps

On Wed, Nov 28, 2012 at 4:30 PM, <a href="javascript:" target="_blank" gdf-obfuscated-mailto="e2JiSl8e_eEJ">jtu...@... <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="e2JiSl8e_eEJ">jtu...@...> wrote:

Cool. So you didn't use some Application's #loaded to put the value into the Smalltalk PoolDict, but misused the config expressions feature. Combined with a packaging rule that includes the constant in the packaged image, that would be exactly what I'm looking for.

I am not sure I fully understood it. Are you saying you used some config expression to set the number and returned false so that it was never used for loading required maps? Dirty and cool at the same time ;-?

I think I like the concept, because I could call some method that does the "heavy lifting" of automatically reading the version name of the config map's loaded edition. 

But as I understand the load order of config maps, I cannot access the edition of the map that is currently in process of loading, right? At the moment a config expression is evaluated, the edition of the map may is most likely not yet loaded, becaus envy will first have to check if it has to load required maps before that . So I'd have to either always use the latest map edition or manage that String manually, right?

So the last piece in my mosaic would be if there is a way to access the map edition from within a configuration expression and I'd buy into this idea instantly!

Thanks for sharing this idea, it sounds promising to me.

But maybe I see another alternative:

Why not use the #loaded method of some Application in the topmost map, that asks for the loaded version of my top map and does the same thing? .... hmmm. gotta think about it.

Joachim
 

Am Mittwoch, 28. November 2012 21:33:52 UTC+1 schrieb RNelson:

My favorite solution was to put "Smalltalk at: #TheApplicationVersionString put: '1.2.7.0 v0' .false" in the base config map "Config. Expressions" field...followed by a "true" line. Then whenever a new map was opened, the version was updated and anyone loading the map would automatically get the correct version. (including the builder). BTW, the "true" line would have the associated required maps, (if any)...

Hope that helps

On Wed, Nov 28, 2012 at 3:24 PM, [hidden email] <[hidden email]> wrote:

Hi,

Do others include some string into their packaged images to indicate the build number or - even better - the version name of some config map or such? How do they do that? 

Almost everything that I can think of has drawbacks, most of them being that some user has to actively do something that ends up in a newly compiled method (whereby the version number of a config map wouldn't be accurate any more unless you first version that stuff and package afterwards...).

Are there any best practices how to do that fully automatically in the packaging process? Where do you keep these numbers/strings? How do you update them?

Just wondering because this would be handy in some situations. Mostly ones that are unpleasant (like users reporting urgent errors friday nights).

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/l1oai8pChQsJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to va-smalltalk...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/DSIlpLDXBPkJ.
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="e2JiSl8e_eEJ">va-sma...@....
To unsubscribe from this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="e2JiSl8e_eEJ">va-smalltalk...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Why not add an empty application in the config map - and the version number of this application IS your application version.
To make it nicer, the developer version the config map and this empty application the same way ?

On Wednesday, November 28, 2012 4:30:11 PM UTC-5, [hidden email] wrote:

 

Why not use the #loaded method of some Application in the topmost map, that asks for the loaded version of my top map and does the same thing? .... hmmm. gotta think about it.

You do want to be careful of what you do in a #loaded method in a headless image - these methods are executed every time the image is started, not just when the image is packaged.

Tom