Skip to content
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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

jecisc
Copy link
Contributor

@jecisc jecisc commented Apr 14, 2023

…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.

…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.
@fniephaus
Copy link
Member

Hi @jecisc could you resolve the conflict so we can merge this?

@jecisc
Copy link
Contributor Author

jecisc commented Oct 11, 2023

Done

baselines
pharoVersionsFrom: aVersion

^ (aVersion to: SystemVersion current major) collect: [ :v | ('pharo' , v asString , '.x') asSymbol ]
Copy link
Member

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'

Copy link
Collaborator

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?

Copy link
Member

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.

Copy link
Contributor Author

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?

Copy link
Member

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')?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants