Closed
Conversation
Author
|
Build failure looks unrelated |
Contributor
|
Since we're now metadataless and #14 as been fixed I wonder whether it would not be better to copy and paste Grease-Pharo60-Core to Grease-Pharo70-Core or Grease-Pharo7-Core. |
Author
|
I noticed kernel class traits have been flattened in Pharo 7. In Magritte that is an issue. Here too? |
Member
|
I agree with @marschall , we have adopted the strategy to copy/paste the packages per Pharo version. If we load the same packages in the different Pharo versions, there is more work to support and understand where somethings needs to be fixed than fixing a bug across all supported platforms. |
Member
|
Added Pharo70 package in aa9e29d |
Member
|
Fixed this in #60 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.