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

bundle config --local gemfile /foo/bar/MyGemfile now works #3312

Closed
wants to merge 1 commit into from

Conversation

dholdren
Copy link
Contributor

  • bundle config can be used to set a custom gemfile name for a
    project (specifying an absolute path)
  • using other bundle commands will now search up parent directories
    for a .bundle dir and use the gemfile specified in .bundle/config if
    it is set
  • does not require a file named 'Gemfile' to exist
  • Revert "Correct bundle-config manpage"
    This reverts commit 0a81457.
  • An added bonus: you can now both set and delete a global bundler
    setting from anywhere: bundle config --delete foo

Manual Test:

In an empty directory /foo/bar/:
echo "source 'https://rubygems.org'" > MyGemfile
echo "gem 'rake'" >> MyGemfile
bundle config --local gemfile /foo/bar/FooGemfile
bundle install
bundle show # Should show the rake gem
mkdir spec && cd spec && bundle show # Should also show the rake gem

- `bundle config` can be used to set a custom gemfile name for a
  project (specifying an absolute path)
- using other bundle commands will now search up parent directories
  for a .bundle dir and use the gemfile specified in .bundle/config if
  it is set
- does not require a file named 'Gemfile' to exist
- Revert "Correct bundle-config manpage"
  This reverts commit 0a81457.
- An added bonus: you can now both set and *delete* a global bundler
  setting from *anywhere*: `bundle config --delete foo`
@dholdren dholdren changed the title Allow bootstrapping non-default gemfile config bundle config --local gemfile /foo/bar/MyGemfile now works Dec 19, 2014
@dholdren
Copy link
Contributor Author

FYI Even though this is technically a new feature, I opened this against 1-7-stable, since it's actually an implementation of an old advertised feature that never worked.

@TimMoore
Copy link
Contributor

@dholdren this is not something that has ever worked in the past, so we won't be merging it to 1-7-stable. Please feel free to open a new pull request against master.

@TimMoore TimMoore closed this Dec 22, 2014
@dholdren
Copy link
Contributor Author

@TimMoore ok, thanks, will do.
I wasn't sure.

@dholdren
Copy link
Contributor Author

reopened as #3320

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.

None yet

2 participants