I'd use it, and the tools you mentioned are not too heavy, but it might create a little confusion too depending on the implementation. Were you thinking of "j___" versions of any binaries (as, e.g. jirb, so jrcov ...)? Or keep the native names?
Anti-bloat is a good principle too, and this might be the first wiggly rock on a slippery slope. I guess my first preference would be to avoid direct packaging, but include some useful scripts that can quickly bootstrap suites of useful gems that work well with JRuby. For example, I am making a lot of Rails apps under JRuby so I keep having to install rails, jdbc-* drivers, jruby-rack, and the lot; this pile is certainly not lightweight, but I want it instantly within reach after installing jruby (so I have my own little script...). Especially in cases where the JRuby gem stack requires some changes from C ruby idiom, this easy bootstrapping could save first time JRuby adopters a lot of digging, and grizzled veterans a lot of repetition. I'm also thinking here of what my Ubuntu boxen do when I type a command but forgot to install the corresponding package: The program 'xpdf' is currently not installed. You can install it by typing: apt-get install xpdf-reader I always like those reminders. Saves me on long-term memory storage. - R On Tue, Oct 27, 2009 at 2:34 PM, Samuel Holloway <shollo...@gmail.com>wrote: > > I can see how it would be helpful to folks that use them but will it create > a headache for folks that want a minimal JRuby install? > >
