I found this strange, too.  I love hoe, I'm just puzzled as to why
it's required by the gems it creates.

Not a dealbreaker; just a curiousity. :)

--Jeremy

On 1/9/07, Ben Bleything <ben / bleything.net> wrote:
> On Wed, Jan 10, 2007, Ryan Davis wrote:
>
> <snip useless file size junk>
>
> > In other words, who cares?!?
>
> At least one other person than me, apparently, since I didn't ask this
> question originally.
>
> > It sounds like you're complaining simply because it offends your
> > sensibilities. If you have a problem with the way gems does
> > dependencies, then file a bug with rubygems and/or offer them a well
> > tested patch. Otherwise, drop it as it doesn't matter one bit.
>
> I'm not really complaining, just asking.  And nobody has answered my
> question yet.
>
> 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.  You're acting
> like I'm insulting your sister, but I'm really just asking a question.
>
> Ben
>
>


-- 
My free Ruby e-book:
http://www.humblelittlerubybook.com/book/

My blogs:
http://www.mrneighborly.com/
http://www.rubyinpractice.com/