-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Finally version libjulia with a proper filename #16362
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
98fe2ad
Finally version libjulia with a proper filename
staticfloat 72a140a
Exclude windows from the versioned shlib fun
staticfloat 5b1d626
Link soversion to Julia version
staticfloat 3b92483
Ensure libjulia symlinks are relative
staticfloat a5b8735
Install libjulia to `$(libdir)` not `$(private_libdir)`
staticfloat fc345d4
Use Major.Minor as <v1.0.0 SOMAJOR
staticfloat 6f1c424
Modify libdl test now that libjulia is not in the private libdir anymore
staticfloat File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
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.
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.
it's allowed to, but in practice we're being stricter than semver
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'd like to remove this line as it's a bit misleading, but I can do it myself later if needed
edit: actually my eyes are going bad, the only thing I'd change is getting rid of the "major"
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.
Well, what I'm going for there is that with the
Major.Minor.Patch
standard,Major
is incremented for large backwards-incompatible changes,Minor
is incremented for large backwards-compatible changes, andPatch
is used for small backwards-compatible changes. Because beforev1.0.0
all the meanings shift down by one decimal place, that means that this line should hopefully be accurate in explaining that the difference betweenv0.4.0
andv0.4.1
is aMinor
bump, not aPatch
bump.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.
Yeah, I think that's mostly covered by the semver spec? In practice we haven't been backporting "major" changes, for some definition of major.
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, I trust your judgement. I'm not married to this comment appearing as-is. Modify as you like. :)