On Jan 10, 2007, at 02:02, Evan Weaver wrote:
> 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.
You fixed this the wrong way. The problem is in RubyGems not
allowing you the ability to distinguish between run-time dependencies
and build-time dependencies.
> 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.
The problem is beyond Hoe's.
Don't fork hoe to fix a problem that exists in RubyGems.
Fix RubyGems instead.
--
Eric Hodel - drbrain / segment7.net - http://blog.segment7.net
I LIT YOUR GEM ON FIRE!