[Ruby] hoe and Manifest.txt

[Ryan Davis]

On Oct 31, 2006, at 9:20 PM, Timothy J. Wood wrote:

> On Oct 31, 2006, at 4:38 PM, Eric Hodel wrote:
>> DO ANY OF YOU ACTUALLY _USE_ HOE?!?!?!
>
>    I'm trying... :)

SWEET.

> diff -r ./lib/hoe.rb /opt/local/lib/ruby/gems/1.8/gems/hoe-1.1.2/lib/
> hoe.rb
> 97c97
> <     "-w -I#{%w(lib bin test).join(File::PATH_SEPARATOR)}" +
> ---
>>     "-w -I#{%w(lib ext bin test).join(File::PATH_SEPARATOR)}" +
> 177c177
> <       dirs = Dir['{lib,test}']
> ---
>>       dirs = Dir['{lib,ext,test}']

Applied, even tho you submitted the worst patch ever. Dude. You  
should know better. Use -u. :P

>    It doesn't look like 'hoe' will check if there is a binary module
> either, so I have ':extensions  => ["ext/extconf.rb"]' in my
> spec_extras.

That actually seems just fine to me. spec_extras has been making me  
happy lately. Do you feel it is sufficient or would you prefer first  
class support?

>    Also, while 'hoe' is required to run the rake tasks, it isn't
> clear why it is added as a dependency in general.  Does the final gem
> actually have any dependencies on 'hoe'?  I'm overriding that for now
> with ':dependencies => []' in my spec_extras.

What will happen is that anyone wanting to unpack said gem will have  
a completely broken rakefile until they figure out they need hoe. So  
if someone wants to submit a patch to you, they have an extra hurdle  
to debug first.

>    So far, though, this is pretty nifty :)

Thanks!