Closed ms closed 12 years ago
Thanks. Bundler 1.1 I see…
We need to be a bit more careful with these…
I swear I'll start using spec more regularly! Now is there any possibility an old bundle would generate "s."?
Sadly, yes. 1.0.27 did it for me yesterday.
The revision that changed it is carlhuda/bundler@86dd35b516b4a017db8d50eb71796bcb101e1d2c
I see that this has been fixed in the code, but the latest gem still doesn't appear to have it.
$ gem search nesta -r | grep "^nesta "
nesta (0.9.13)
$ bundle | nesta grep
Using nesta (0.9.13)
$ bundle exec nesta plugin:create foobar
create nesta-plugin-foobar/Gemfile
create nesta-plugin-foobar/Rakefile
create nesta-plugin-foobar/LICENSE.txt
create nesta-plugin-foobar/README.md
create nesta-plugin-foobar/.gitignore
create nesta-plugin-foobar/nesta-plugin-foobar.gemspec
create nesta-plugin-foobar/lib/nesta-plugin-foobar.rb
create nesta-plugin-foobar/lib/nesta-plugin-foobar/version.rb
$ ack "s.add_" ./nesta-plugin-foobar/nesta-plugin-foobar.gemspec
s.add_dependency("nesta", ">= 0.9.11")
s.add_development_dependency("rake")
Should this be considered open until it's released?
I really need to get 0.10.0 out. Sorry.
I'd rather not re-open bugs until they've been released though; GitHub doesn't seem very well suited to that (i.e. there's no "Implemented but not released" status).
In nesta's .gemspec, we use 's', but
bundle gem
generates a .gemspec file using a variable 'gem'.