-
-
Notifications
You must be signed in to change notification settings - Fork 2k
bundle package -- all && bundle install --local fails to install #2494
Comments
I can reproduce this with a very simple skeleton project: https://github.com/TimMoore/bundler_issues_2494 Clone that and then run |
It looks like you can work around this by removing the |
Well what do you know. I guess that's a good work around. I can use that for now. Thanks :) |
Running On Jun 15, 2013, at 6:31 AM, Raul E Rangel [email protected] wrote:
|
So as a short-term solution for 1.x, should |
Another strange thing: |
Yeah, I think patching --local to also set --no-cache makes sense for 1.x. On Sat, Jun 15, 2013 at 6:46 PM, Tim Moore [email protected]
|
Fixed by #2509. The fix should be in 1.3.6 and 1.4.0 when those are released. |
Setting |
What you're trying to accomplish
I have a directory structure like so
My Gemfile contains a relative path to my-gem
I'm trying to package up my gems into the
vendor/cache
folder so I can easily deploy it to my production servers. My deployment artifact will only contain the contents ofapp
.The command you ran
On the build box I ran
This installed all my gems dependencies into
vendor/cache
including all my git and path dependencies. It also updated theGemfile.lock
to show the path asvendor/cache/my-gem
.I transported the
app
folder to my production server and didWhat you expected to happen
When running with
--local
bundle should install all the gems in the vendor/cache.What actually happened
Bundler installed the gems but then tried to update vendor/cache and failed due to the fact that the actual source of the gems does not exist.
The exception backtrace(s), if any
Everything output by running bundle env
My thought is that bundle install --local should not try and update the vendor/cache folder.
The text was updated successfully, but these errors were encountered: