[LRUG] November talk proposal

[Viktor Trón]

Tom's solution can be achieved by setting global options to bundler:

$ cat ~/.bundle/config
---
BUNDLE_BUILD: --no-ri --no-rdoc
BUNDLE_PATH: .bundle/gem
BUNDLE_BIN: .bundle/bin

thus works even if bundle is called by your IDE or whatever

I'm starting to get really confused about rvm/gemsets/bundler
If you bundle per project, why would you need gemsets with rvm, i would
even say rvm info will totally mislead you with $GEM_HOME etc
on the other hand if you just use rvm gemsets, why would the binpath ever
get confused (provided you use the right gemset)?

your insights appreciated

Vik

On Thu, Oct 11, 2012 at 11:29 AM, Jim Myhrberg <contact at jimeh.me> wrote:

> On Thursday, 11 October 2012 at 10:38, James Adam wrote:
>
> Using bundler with binstubs and including the relative path '.bundle/bin'
> in your PATH has pretty much entirely removed the need to run bundle exec
> for me, Tom Ward and at least a few others. I highly recommend this:
> http://tomafro.net/2012/06/tip-bundler-with-binstubs
>
> I'm doing the same thing with just a slight variation to the binstub path.
> Additionally I also bundle all gems relative to the project. For details
> check my blog post on the topic:
>
> http://jimeh.me/blog/2011/11/01/my-ruby-development-environment/
>
>
> -jimeh
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20121011/5bfa968c/attachment-0003.html>