-
-
Notifications
You must be signed in to change notification settings - Fork 2k
bundle directory structure differs depending on where BUNDLE_PATH is specified #2987
Comments
It was hardcoded that way :/ Undoing that for Bundler 2 would be great, and pulls to the 2-0-dev branch are welcome. On Fri, Apr 18, 2014 at 10:55 AM, Jack Nagel notifications@github.com
|
:/ I assume the desirable behavior is to always use the |
Yup, that’s the one. On Apr 18, 2014, at 11:18 AM, Jack Nagel notifications@github.com wrote:
|
I think 841881f makes this work as intended for 2.0. Using the
This looks fixed with a 2.0 release. 👍 |
Closing since this is already fixed on the 2.0 branch, thanks. |
Wow, this inconsistency was making me think I'd lost my mind. Any chance of getting this fix backported into 1.8? |
Unfortunately that would break backwards compatibility, so we can't do it until 2.0.
|
First, here's a gist of
bundle env
along with an illustration of the problem: https://gist.github.com/jacknagel/11055804My global config looks like:
It seems that, depending on whether BUNDLE_PATH is specified globally in ~/.bundle/config or locally in .bundle/config changes the resulting structure of the bundle.
If specified only globally, then the resulting directory structure looks like:
However, if I also specify it in .bundle/config, then I get:
and
Being unfamiliar with the bundler codebase, I wasn't able to determine why this would happen. If someone could shed some light, that would be great.
If I've omitted anything, please me know, I'm happy to provide more information but I'm unsure what else will be helpful.
The text was updated successfully, but these errors were encountered: