On Wed, Feb 11, 2009 at 6:05 PM, Dan Kubb (dkubb) <[email protected]> wrote: > > Hi Everyone, > > I've seen a few tweets and blog posts over the last few months talking > about Merb and DataMapper, and how dealing with gems are a dependency > nightmare. >
Better way to explain this is do it graphically: http://gist.github.com/62222 > I don't doubt it is a problem in some cases, but I want to learn why, > and see if there's a way to resolve it.. or at the very least lessen > the problem. There are several ways to resolve this, some are manifest of gems used and using bundling that exists in merb. The other is turn smaller gems with similar purposes into bigger ones (so mentioned flexibility). > Can anyone provide some specific examples where this has been a > problem for you? Any other feedback or ideas? > Cannot provide examples for Merb, but something I found quite often is the need to remember how many gems I need to install in the servers (and which versions), either via ssh or automated deploy/bundling. An example of going from -core and -more gems back into one is Sequel, they merged both back when version 2.3.0 came out. Anyway, just ranting :-P -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exupéry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
