Ryan Davis wrote:
> 
> On Oct 1, 2006, at 2:29 AM, Minero Aoki wrote:
> 
>> I don't now about Rake, but why Rake calls fu_check_options?
>> Adding new methods to FileUtils module?
> 
> Yes. In particular: #sh, #ruby, and #safe_ln.
> 
>> I think fu_* method is library private (so I explicitly use
>> :nodoc: directive), other library should not depend them...
> 
> While I agree, they are depending on the fu_* methods simply because of 
> their general utility. Rake is has a very large install-base, being the 
> 5th most downloaded gem and the 12th most directly downloaded project on 
> rubyforge, so the impact can be rather big, where this version in CVS 
> isn't widely used yet... I don't see a functional difference with the 
> splatted version so that is why I asked. If it impacts future plans, 
> then it makes sense to leave it as-is and make those using private 
> methods deal with the violation.
> 
> BTW, I've already sent email to Jim Weirich about rake, but I think he's 
> been out of town for the weekend or something.

It looks like rake's dependency on fu_check_options and 
fu_output_message is pretty lightweight.  I can remove those dependencies.

-- Jim Weirich