-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Each time a version of Pharo is released we need to update the baseli… #595
base: master
Are you sure you want to change the base?
Conversation
…ne if we want to be able to be able to load smalltalk CI in the new Pharo version. Here is a little improvement to not have to do that again.
Hi @jecisc could you resolve the conflict so we can merge this? |
Done |
baselines | ||
pharoVersionsFrom: aVersion | ||
|
||
^ (aVersion to: SystemVersion current major) collect: [ :v | ('pharo' , v asString , '.x') asSymbol ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Turns out this only works in Pharo:
a MessageNotUnderstood occurred (error 2010), a Set does not understand #'current'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works in Squeak 5.1 as well. Is that error from GS?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know tbh.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to know if we are on Pharo, Squeak or Gemstone that works in all smalltalks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, but do we really need to complicate this even more? I forgot about the semantics, but maybe the spec could just target #'pharo'
instead (or #'pharoCommon'
?) and then we have specific overrides for Pharo < 5 (e.g. #'pharo4.x'
)?
…ne if we want to be able to be able to load smalltalk CI in the new Pharo version.
Here is a little improvement to not have to do that again.