-
-
Notifications
You must be signed in to change notification settings - Fork 9.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
Enable ruby-macho by default. #767
Conversation
Flips HOMEBREW_RUBY_MACHO to HOMEBREW_NO_RUBY_MACHO.
In what situation(s) would one set that? I'm wondering if it's worth just deleting the existing code now? |
In the unlikely event that we run into any bugs immediately after rolling this out, we could tell people to set I discussed this with @UniqMartin in a PM on slack, and 2-3 weeks seems like a good rollout period to us. If nothing substantial happens after that, we can simply delete the |
👍 seems like a good plan to me. |
As already mentioned by @woodruffw, that's a temporary measure suggested by me. The other motivation is to ship this feature and thus formally finalize William's GSoC project (with the stated goal of enabling the code for all Homebrew users) with a minimal PR that can be shipped more quickly than a thorough cleanup. (But we definitely aim for a proper cleanup.) |
Hooray 👏 |
Thanks @woodruffw; great work! 🎉 And sorry for the delay … |
No problem! Glad to 🚢 this out! |
@woodruffw @UniqMartin can definitely 💀 the old code now I think! |
Got it! I'll have a PR ready in a few 😄 |
brew tests
with your changes locally?Flips
HOMEBREW_RUBY_MACHO
toHOMEBREW_NO_RUBY_MACHO
.I also deleted the
HOMEBREW_RUBY_MACHO
enablement line intest-bot
, since this PR enables it by default (and no longer checks that variable).