Michael Klishin wrote: >> But I thought everything was pluggable, so I could just leave out >> the pluggables >> that needed it, like merb-action-args...
> RubyGems have no concept of "partial meta gems", so merb-more depends > on all of -more gems, that, in turn, carry ParseTree dependencies around How heavy and fragile must a leaf dependency get before y'all boot it out of the default stack? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
