Warn if RUBYGEMS_GEMDEPS is set

[segiddins]

Should we do this so there's less confusion when rubygems and bundler clash?

[indirect]

How do they clash? And yes, that seems likely :/

On Sat, May 16, 2015 at 7:38 PM, Samuel E. Giddins
[email protected] wrote:

Should we do this so there's less confusion when rubygems and bundler clash?

Reply to this email directly or view it on GitHub:
#3656

[segiddins]

If rubygems in any resolves things differently than bundler, we might not be able to setup our environment correctly. Haven't we also had issues with things like rubygems-bundler in the past?

[indirect]

I have no idea what happens if you set RUBYGEMS_GEMDEPS and also use Bundler. I guess we should check?

As for rubygems-bundler, that was broken because of trying to automatically bundle exec not because of RUBYGEMS_GEMDEPS. But yes, definitely issues.

[agis]

Does a warning on every CLI command along the lines of

RUBYGEMS_GEMDEPS` is set and this may cause bundler to conflict with rubygems

sounds sufficient?

[segiddins]

@agis- yeah

[ioquatix]

Is this still relevant? It's nice that I don't have to use bundle exec everywhere. With bundler and rubygems merging, can we find some consensus on this?