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

Enable ruby-macho by default. #767

Merged
merged 1 commit into from
Aug 23, 2016

Conversation

woodruffw
Copy link
Member

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same change?
  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your changes? Here's an example.
  • Have you successfully run brew tests with your changes locally?

Flips HOMEBREW_RUBY_MACHO to HOMEBREW_NO_RUBY_MACHO.

I also deleted the HOMEBREW_RUBY_MACHO enablement line in test-bot, since this PR enables it by default (and no longer checks that variable).

Flips HOMEBREW_RUBY_MACHO to HOMEBREW_NO_RUBY_MACHO.
@MikeMcQuaid
Copy link
Member

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?

@UniqMartin UniqMartin added the gsoc-outreachy Google Summer of Code or Outreachy label Aug 20, 2016
@woodruffw
Copy link
Member Author

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 HOMEBREW_NO_RUBY_MACHO as a quick fix.

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 cctools-based implementation and the environment checks associated with it.

@MikeMcQuaid
Copy link
Member

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 cctools-based implementation and the environment checks associated with it.

👍 seems like a good plan to me.

@UniqMartin
Copy link
Contributor

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?

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.)

@UniqMartin UniqMartin merged commit cb700b6 into Homebrew:master Aug 23, 2016
@MikeMcQuaid
Copy link
Member

Hooray 👏

@UniqMartin
Copy link
Contributor

Thanks @woodruffw; great work! 🎉 And sorry for the delay …

@woodruffw
Copy link
Member Author

No problem! Glad to 🚢 this out!

@MikeMcQuaid
Copy link
Member

@woodruffw @UniqMartin can definitely 💀 the old code now I think!

@woodruffw
Copy link
Member Author

Got it! I'll have a PR ready in a few 😄

@woodruffw woodruffw deleted the ruby-macho-enable branch September 20, 2016 21:30
@Homebrew Homebrew locked and limited conversation to collaborators May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
gsoc-outreachy Google Summer of Code or Outreachy
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants