From: Ryan Davis <ryand-ruby@...>
Date: 2007-01-10T15:52:48+09:00
Subject: Re: [ANN] Tattle - The Ruby Census


On Jan 9, 2007, at 11:33 PM, Ben Bleything wrote:

> It's not a problem with the way gem handles dependencies.  It's a
> problem with hoe injecting itself as a dependency on any gem it  
> creates.
> And it's not really a problem, I just want to know why.

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'"). That would include rake if  
you have a Rakefile. Since a Rakefile is just software (a  
specification for automated behavior), it too can have dependencies.  
Since hoe projects are just rakefiles that use hoe, it has a  
dependency on hoe... Without hoe as a dependency, the software  
packaged in a hoe-based gem doesn't work 100%.  But... you're a smart  
guy. You knew that.