Binstubs made by Rails 4 are different from those made by Bundler 1.3 (pre5)

[jlecour]

Hi,

I'm working on a Rails 4 app (using 555cb0a) and Bundler 1.3.0.pre.5.

When I execute bin/rake rails:update I end up with those binstubs :

#!/usr/bin/env ruby
APP_PATH = File.expand_path('../../config/application',  __FILE__)
require_relative '../config/boot'
require 'rails/commands'

#!/usr/bin/env ruby
require_relative '../config/boot'
require 'rake'
Rake.application.run

And later if I bin/bundle they are changed back to :

#!/usr/bin/env ruby
#
# This file was generated by Bundler.
#
# The application 'rails' is installed as part of a gem, and
# this file is here to facilitate running it.
#

require 'pathname'
ENV['BUNDLE_GEMFILE'] ||= File.expand_path("../../Gemfile",
  Pathname.new(__FILE__).realpath)

require 'rubygems'
require 'bundler/setup'

load Gem.bin_path('railties', 'rails')

#!/usr/bin/env ruby
#
# This file was generated by Bundler.
#
# The application 'rake' is installed as part of a gem, and
# this file is here to facilitate running it.
#

require 'pathname'
ENV['BUNDLE_GEMFILE'] ||= File.expand_path("../../Gemfile",
  Pathname.new(__FILE__).realpath)

require 'rubygems'
require 'bundler/setup'

load Gem.bin_path('rake', 'rake')

Which of those should I keep?

Thanks

[rafaelfranca]

@hone @jeremy

[jeremy]

This will be fixed in the next bundler --pre release. It won't overwrite executables you already have in ./bin

[jlecour]

It was fine with pre-releases (including pre.8), but with the 1.3.0 release I get overwritten binstubs every time I bundle, bundle update or bundle install.

I'm using Rails 4.0.0.beta1, Ruby 2.0.0-p0 and Bundler 1.3.0 with Rbenv 0.4.0 on Mac OS X 10.8.2.

[jeremy]

Bundler reverted this change for semver compliance. To avoid it, don't use bundle install --binstubs which "sticks" the binstubs option in .bundle/config. To fix it now, you can wipe the sticky config. Sorry about that!

[jlecour]

@jeremy Thanks, but what if I want to create binstubs, only not overwriting them when they are already present?

[jeremy]

@jlecour Use the new bundle binstubs <gemname> command.

[epipheus]

so is there a Rails 4 friendly way to create all binstubs without individually specifying the names of each executable. Currently I do: bundle install --binstubs and then rake rails:update:bin

[steveklabnik]

The idea is that you should do them individually; gems provide lots of executables you may or may not use. It's a one-time thing that doesn't take very long.

You shouldn't be using --binstubs with rails 4.

[epipheus]

Why shouldn't it be one's choice whether to have binstubs of everything or
just a few?

[chrismo]

Bundler did attempt to change itself to not overwrite bin entries on every invocation, so that the rails entry would be left alone, but this wasn't backwards compatible, so it was reverted: rubygems/bundler@f00e085

I agree with you about the way it should be - it was perhaps a hasty move by Rails to stick its business into the bin directory.

FWIW, in practice I find I don't have many bin-able gems and handling them one at a time has not been a big deal.