-
-
Notifications
You must be signed in to change notification settings - Fork 2k
package & install fails with local gem paths #2921
Comments
I believe that package —all currently does not work for :path gems. I’d like to fix this as soon as I have time, and in the meantime pull requests to fix the issue are welcome. On Mar 9, 2014, at 4:17 PM, Patrick Hemmer notifications@github.com wrote:
|
The "what's new" for version 1.2 explicitly states that it does. Edit: |
When I say "currently does not work", I mean that it has been broken by a bug. Sorry it's not working right now. :( On Sun, Mar 9, 2014 at 4:26 PM, Patrick Hemmer notifications@github.com
|
If the path happens to be a git repo, just use |
fixed in 0efe021. |
Bundler 1.2 added the ability for
bundle package --all
to include local and git gems. However when installing the generated package it fails in multiple different ways.By multiple different ways, I don't mean the result is random, I mean the behavior is very different based on changes that shouldn't have any impact (I would think).
Here's a script which duplicates the issue (
bug.sh
):When run as
bug.sh
you get the following output (snipped to relevant bit):Here you can see the output first shows it's using the gem from the
vendor/cache
as it should. Then it fails when it tries to use the non-cached version which is missing.However by changing one little bit, adding a gem from git (installs the 'robotarmy/example' gem), the error message is completely different.
Run as
bug.sh 1
:I get this behavior with version 1.3.5 and 1.5.3.
No RVM
The text was updated successfully, but these errors were encountered: