16:22 <blackmesa> Hi all. anybody can explain me what 'bundle install ... --binstubs' means? it does install the gem folders and binaries inside the application folder?

16:51 <mfoo> blackmesa, the gem binaries will be put into the bin folder by default, yes

19:16 <blackmesa> mfoo: what are the advantages of using binstubs?

19:30 <blackmesa> is it only for development environment?

19:32 <indirect> blackmesa: --binstubs adds additional executables to the bin/ (or whatever path you pass to --binstubs) directory

19:32 <indirect> those binstubs will automatically set up the bundled environment

19:33 <indirect> meaning that you don't need to use bundle exec

19:33 <indirect> typically that makes the startup time for the command faster

19:33 <indirect> you can use binstubs while deploying too

19:33 <indirect> but keep in mind that if you use rails, rails has already claimed bin/rails and bin/rake

19:33 <indirect> and you break things if you override them

19:34 <indirect> so you probably want to use `bundle binstub GEM [GEM [GEM]]` to generate binstubs instead

19:34 <indirect> only for the gems you care about

19:50 <blackmesa> indirect: thx

22:52 <prahal> hi I have collision between gems about identifier for https://github.com/bundler/bundler/blob/master/lib/bundler/lockfile_parser.rb#L128 <- where identifier comes from https://github.com/bundler/bundler/blob/master/lib/bundler/lazy_specification.rb#L65 on arm A9 (ruby 1.9.3)

22:52 <prahal> gist exhibiting the issue at https://gist.github.com/prahal/7571353

22:54 <prahal> I cannot reproduce on either amd64 or i386 arch . Though I worked around the issue (which was that when sub-setter (required by fast, itself required by sequel-fixtures - and discoverer both at 0.0.2 version discoverer is found first and then sub-setter discarded as the key of the @specs is taken

22:55 <prahal> thus I end up with the dreaded : 'require': Cannot load such file -- sub-setter (LoadError)

22:56 <prahal> mind that the sub-setter gem has an issue in the packaging : half of its files are readable only by owner which ends up root here . thus I first had the same error but about sub-setter/sub-setter (which was one of those root only readable files)

22:57 <indirect> prahal: if you have a question, feel free to ask it, or check out bit.ly/bundler-issues for troubleshooting tips