From: Evan Weaver <eweaver.spamtrap@...>
Date: 2007-01-10T19:02:26+09:00
Subject: Re: Tattle - The Ruby Census

Ryan Davis wrote:
> No, hoe is acting absolutely properly when it injects itself into the
> dependency list. Any gem should FULLY list all of its dependencies it
> requires to work (defined broadly by rubygems but could be summarized
> as "something mentioned by 'require'"). 

There is a difference of opinion here. Ryan thinks dependencies should 
include meta-dependencies. Many people, though, do not. The question has 
come up before:

http://rubyforge.org/tracker/index.php?func=detail&aid=5993&group_id=1513&atid=5921
http://rubyforge.org/tracker/index.php?func=detail&aid=7118&group_id=1513&atid=5922

I agree with those who want to avoid installing meta-dependencies on 
production servers. So, here is Echoe, a Hoe 1.1.6 fork.

sudo gem install echoe

http://rubyforge.org/frs/?group_id=2835

To use Echoe properly in a Rakefile, load it conditionally, like so:

require 'rubygems'
require 'rake'
begin
  require 'echoe'
  # all your regular Echoe config
rescue LoadError => boom
  puts "You are missing a dependency required for meta-operations on 
this gem."
  puts "#{boom.to_s.capitalize}."
  desc 'No effect.'
  task :default; end
  # if you still want tests when Echoe is not present
  desc 'Run the test suite.'
  task :test do
     system "ruby -Ibin:lib:test some_tests_test.rb" # or whatever
  end
end

Personally, I hate Echoe. There is no reason to fork. But I think that 
there is a need here, and if the Hoe developers refuse to acknowledge 
it, we have no  choice.

Evan Weaver

PS. Ryan, I submitted a patch against Rubyforge 0.4.0 for some stuff.
http://rubyforge.org/tracker/index.php?func=detail&aid=7727&group_id=1024&atid=4027


-- 
Posted via http://www.ruby-forum.com/.