I love the concept of `bundle package --all`, since it takes the awesomeness of `bundle package` and makes it work magically with git sources as well. But: after trying to adopt it on a good sized project, we had to go back to the bad old days of just `bundle package`.
The problem's pretty simple: `--all` caches the gem directory, in a <name>-<ref> format, and causes ridiculous amounts of repository churn every time the dependency updates. Since git-backed gems are often the *most* likely to change - we use them all the time for private shared code that we change fairly regularly, or to track projects closely that change more frequently than they cut releases - the noise got to the point where we couldn't take it anymore and we had to can it.
I'd like to propose - and offer to implement a first pass of - `bundle package --all` actually building and caching a <name>-<ref>.gem file instead of the unpacked gem directory. Will this work or am I missing something that makes it infeasible? Would the bundler team be amenable to such an approach and a patch to implement it? Is there somewhere else I should be asking these questions?
Thanks,
--
Nathaniel