From: Richard Kilmer Date: 2004-08-17T22:31:15+09:00 Subject: Re: Recursive install-stub for gems? On 8/17/04 8:05 AM, "Austin Ziegler" wrote: > On Tue, 17 Aug 2004 16:21:10 +0900, Robert Feldt wrote: >> Gavin Sinclair wrote: >>> On Tuesday, August 17, 2004, 10:52:48 AM, Chad wrote: >>>>> Shouldn't "gem install X --install-stub" work recursively so that not >>>>> only the top-level loading of the gem is done but it also works for >>>>> files deeper down in the dir? >>>> You're not missing anything. We're planning to add the ability to >>>> specify other files that can be stubbed. Right now, though you *can* >>>> do: >>>> require_gem 'net-ssh' >>>> require 'net/ssh/sftp' >>>> Would our proposed change work? We are avoiding stubbing every single >>>> file in the lib, and allowing gem authors to specify the ones that >>>> would make sense (as in sftp). >>> Thanks for answering, Chad. I'm working on this feature at the >>> moment. > >>> Robert and others: should it stub every file, or should gem authors >>> decide which files are to be stubbed? >> Chad and others: I think the latter solution is best; stubbing every >> file seems awkward and the author can influence what people expect to be >> stubbed in the docs etc. I wouldn't mind spec'ing it in the GemSpec. > > Why not offer both? That is, give the spec author a simple token that > can be detected to stub everything in the lib directory? > > -austin Well, because is rather defeats the purpose of keeping the files out of the site_ruby dir. -rich