-
-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
vtk: drop clang 1316 workaround #209097
Open
cho-m
wants to merge
1
commit into
master
Choose a base branch
from
vtk-drop-clang-1316
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+0
−18
Open
vtk: drop clang 1316 workaround #209097
Changes from all commits
Commits
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
Oops, something went wrong.
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.
Probably need
depends_on "expat"
to avoid breaking installs on macOS 15. See also Homebrew/brew#19315There 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.
This is part of the odd situation of dependents of Python now propagating
expat
. Essentially will end up with dozens of formulae with brewexpat
linkage unless we handle this differently.Some alternatives:
expat
on Ventura/Sonoma #207887brew
superenv and removeexpat
if only a dependency of[email protected]
Or we just accept
expat
usage everywhere.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.
Seems fine to accept it in dependents to me. There's already linkage anyway.
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.
The formulae impacted (i.e. those with
uses_from_macos "expat"
and[email protected]
in dependency tree) are:There were originally more before removing
[email protected]
fromglib
runtime dependencies.One thing about current state is there is a higher risk of mixing
expat
libraries when installing a combination of Sequoia and Sonoma bottles, i.e. formula bottled/built on Sequoia may be linked to system expat but Sonoma bottle was linked to brew expat and then a project that combines these may crash from multiple expat.Though we don't really care about this for
ncurses
andlibxml2
dependents which has similar concerns.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.
Anyway, the existing
vtk
bottle is still linked to systemexpat
so we shouldn't modify dependency until new bottle is needed:Either on next version bump or revision bump like #207100