From: Nathaniel Talbott <ntalbott@...>
Date: 2007-01-11T08:15:34+09:00
Subject: Re: Tattle - The Ruby Census

On 1/10/07, Christian Neukirchen <chneukirchen@gmail.com> wrote:

> It is easy to write a rakefile that downgrades itself.  Possible gem
> hackers will have hoe installed anyway, there is no need to declare
> this dependency.

Yes, but in order for the Rakefile to do *anything*, rake would have
to be installed, which it wouldn't necessarily be unless Hoe is a
dependency.

FYI, I originally stripped the hoe dependency from cooloptions, and
have since added it back after further consideration. I'd love to have
development dependencies separated out from runtime dependencies, but
until then, the hoe stays in.

A thought: if code that's not used at runtime is such an issue,
shouldn't we be stripping tests, Rakefiles and the like from our
libraries before gem'ing them? I don't see the difference between
those files and the hoe dependency.

Just my $0.02,


-- 
Nathaniel Talbott

<:((><