gemspec dependencies definition and require conflict

Question

I have a conflict between the gem dependencies definitions and the require of these gems.

I have this:

# Gemfile
source "http://rubygems.org"
gemspec

-

# my_gem.gemspec
$:.push File.expand_path("../lib", __FILE__)
require "my_gem"

Gem::Specification.new do |s|
  s.version = MyGem::VERSION
  # ...
  s.add_dependency "s3"
end

-

# /lib/my_gem.rb
require 'rubygems'
require 's3'

The conflict line is the s3 requirement because when I execute bundle install it complains because this gem is not installed yet.

The workaround is to comment this require, then execute bundle install and uncomment the require again what is not pretty at all.

Any suggestion is welcome, if you need more details to understand the problem please tell me.

score 3 · Accepted Answer · answered Jul 25 '11 at 20:33

3

First, don't require your entire gem in your gemspec. Move your version info to a path like "lib/my_gem/version.rb" and require that. Secondly, you shouldn't do a "require 'rubygems'" unless you're using the Rubygems API for some feature. There are some users that don't use Rubygems, and you shouldn't force them to use it unless necessary.

answered Jul 25 '11 at 20:33

semmons99

1,134
1
9
13

working as a charm, thanks.. and also thanks for the **not require rubygems** tip, I have been reading about this, I have changed my _require_ by this other: https://gist.github.com/1105149 – fguillen Jul 25 '11 at 20:44
1

As your library is gona be run with rubygems, there is no need to require rubygems at all. When testing, for examples binaries, use ruby -I lib -rubygems bin/mybinnary – Guillermo Jul 25 '11 at 22:59
rubygems is built in to ruby 1.9.3 so it's a non-issue from there on. – Matt Connolly Apr 03 '12 at 21:11

score 1 · Answer 2 · answered Jul 25 '11 at 22:38

1.- Do not require 'rubygems' in a library. Is like if a unix program requires apt-get, so no other system can't use your library.

2.- In the library, put your version in a separate file /lib/lib_name/version.rb and require that file on gemspec. Only that file, so you don't load your library and dependecies when trying to loading the gemspec.

gemspec dependencies definition and require conflict

2 Answers2