Glenn, Plugins don't handle dependencies and versioning. Right there you have 2 major reasons to use plugins. On top of that, you need to install the same library on each of your project instead of reusing the installed lib.
Does it make sense? -Matt On 3/3/08, Glenn Little <[EMAIL PROTECTED]> wrote: > > > Thanks... I'll look into the suggestions when I get a sec. Why > are plugins evil? Seems like a pretty clean way to > extend rails on a per-app basis...? > > > -glenn > > > Matt Aimonetti wrote: > > Technoweenie has a small plugin that lets you do that: > > http://svn.techno-weenie.net/projects/plugins/gems/ > > > > Otherwise you can try gemsonrails > > https://rubyforge.org/projects/gemsonrails/ > > > > Both libs let you do the same thing: freeze and package a gem. > > > > -Matt > > > > p.s: plugins are somewhat evil and that's why Merb only uses gems. > > > > On 3/3/08, *Glenn Little* <[EMAIL PROTECTED] > > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > > Is there an easy way to install a gem locally into a single > > app without messing with the ruby environment (basically, as > > if it were a plugin)? For instance, say I wanted to install > > Matt's Gchart code as a plugin. > > > > I tried just untarring the code into vendor/plugins dir, but > > the rhtml page on which I call Gchart bombs with an unexpected > > nil on a seemingly unrelated line several lines above the > > Gchart call. It was a longshot anyway. > > > > Thanks. > > > > -glenn > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
