I like the style of the Merb plugin manager....installing gems straight from RubyForge.
However, the current implementation in trunk wants to find an install script and a Rakefile.merb. Many gems would still be useful without this and could be easily packaged with a Merb app for deployment. Right now it wil "rescue nil" if no uninstall script is found, but the others are required. Is there any objection to tweaking the code so it looks for install and rakefile.merb, but doesn't require them for a successful plugin installation? -- Geoffrey Grosenbach ........................ Blog | http://nubyonrails.com Podcast | http://podcast.rubyonrails.com Screencast | http://peepcode.com _______________________________________________ Merb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/merb-devel
