Mike McQuaid

Results 582 comments of Mike McQuaid

The main problem I believe is that these all install into the same prefix rather than individual Cellars. That alone I think makes this not very Homebrewy and I'd personally...

@Bo98 Note: this is exactly the same issue I was hitting when trying to add `base64` to the `Gemfile` in https://github.com/Homebrew/brew/pull/17315.

> This behaviour is expected behaviour from Bootsnap as it expects gems installs to be stable. What does this mean? > The only workaround here is manually removing the base64...

Have opened https://github.com/Homebrew/brew/pull/17343 and https://github.com/Homebrew/brew/pull/17342 to start working around this stuff and get this PR merged.

> Not really when it's something very widely agreed on in the Ruby community: [rubocop/rubocop@b2b29da](https://github.com/rubocop/rubocop/commit/b2b29da6406ed55fe42fe045435c29bed6635299), [rack/rack@696ed9e](https://github.com/rack/rack/commit/696ed9e8f48053683a0a19fc68eb49f094c0efcb), [lostisland/faraday@9487833](https://github.com/lostisland/faraday/commit/9487833b426ad1c50d6d8a29d82601202a528c56), [octokit/octokit.rb@a787bf4](https://github.com/octokit/octokit.rb/commit/a787bf47377229688eea4b6c78b26b584f65595b) Note that Octokit still adds it to the `Gemfile`. I still consider...

> Yes, there's a PR open that I reckon will solve this: [rubygems/rubygems#7673](https://redirect.github.com/rubygems/rubygems/pull/7673) @Bo98 Great, seems like the best option here, good find. Here's a thought: what if we pushed...

> Having `bundle clean` in vendor-gems and keeping the existing one in utils/gems.rb will likely be sufficient, given the issues is caused by `--standalone` and the only occurrence of that...