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

21508-Integrate-Calypso-0103 #1037

Conversation

dionisiydk
Copy link
Contributor

#loadCalypso script is now uses Metacello locking mechanizm to force explicit version for all dependencies.
Calypso version is now 0.10.3.

https://pharo.fogbugz.com/f/cases/21508/Integrate-Calypso-0-10-3

…explicit version for all dependencies.

Calypso version is now 0.10.3.
Strangely lock guard is not working here. But this script works well in Pharo 6.
Let's try another way to handle lock signal.
@dionisiydk
Copy link
Contributor Author

Looks like this lock API do not work in Pharo 7.

But it not works anyway
While locking does not work we can just load required dependency versions
@MarcusDenker MarcusDenker merged commit 2eb9bd2 into pharo-project:development Mar 6, 2018
@guillep
Copy link
Member

guillep commented Mar 7, 2018

No, it's not the lock API that is wrong, you're using it wrong.

Also, BaselineOfCalypso is still wrong. We should depend on exact versions on release.

			baseline: 'ClassAnnotation' with: [
				spec
					repository: 'github://dionisiydk/ClassAnnotation:v0.3.x';
					loads: 'Core' ];
			project: 'ClassAnnotationTests' copyFrom: 'ClassAnnotation' with: [
				spec loads: 'Tests'];
			baseline: 'Commander' with: [
				spec repository: 'github://dionisiydk/Commander:v0.5.x' ];
			baseline: 'SystemCommands' with: [
				spec repository: 'github://dionisiydk/SystemCommands:v0.7.x' ].

Moreover, this change is plain wrong:

https://github.com/pharo-project/pharo/pull/1037/files

We should just load Calypso and not all of its dependencies.

We should put the exact versions in the baseline, and you should use lock in your development image.

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