Skip to content
This repository was archived by the owner on May 14, 2021. It is now read-only.

COOK-3219: Using omnibus bundler for your app is bad#31

Merged
jtimberman merged 1 commit intopoise:masterfrom
lamont-granquist:COOK-3219
Jun 27, 2013
Merged

COOK-3219: Using omnibus bundler for your app is bad#31
jtimberman merged 1 commit intopoise:masterfrom
lamont-granquist:COOK-3219

Conversation

@lamont-granquist
Copy link
Copy Markdown
Contributor

  • default behavior is still unchanged
    • allow user overriding env
    • introduce "use_omnibus_ruby" true/false switch
    • complain at people doing it wrong

  - default behavior is still unchanged
  - allow user overriding env
  - introduce "use_omnibus_ruby" true/false switch
  - complain at people doing it wrong
@lamont-granquist
Copy link
Copy Markdown
Contributor Author

This is one option to address the problem. This is the least intrusive to everyone's workflow, and should probably be temporarily put in to warn people that behavior will be changing in the future.

I would be happy to make the default behavior to not use omnibus' ruby. We definitely need to get here.

I would be extremely happy to simply revert COOK-744 with extreme prejudice and force people to hack up their environment manually if they really want their app to be tied to omnibus ruby...

Comment thread providers/rails.rb
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it seems these could be named with more clarity.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this sets PATH to Gem.default_bindir and then the existing PATH, unless the user specifies a PATH.

jtimberman pushed a commit that referenced this pull request Jun 27, 2013
COOK-3219:  Using omnibus bundler for your app is bad
@jtimberman jtimberman merged commit 5f7acac into poise:master Jun 27, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants