Except there is no real concept of versions with plugins. Starting with simple dependency requirements of "plugin X requires plugin Y" would make me happy for now.
On 9/19/07, Pratik <[EMAIL PROTECTED]> wrote: > > > I didn't intend my post to be a personal attack, and I'm sorry that it made > > you feel attacked. I didn't make any statements about your person; it's > > your position that I questioned. > > > > Point taken. No worries :) Thanks for clearing the air. > > > > > Sorry for the novel. Executive summary: These aren't new problems. Let's > > learn from at old solutions. > > Exactly. That's why plugins as gems approach is better, as you can > have versioning of your plugins and any other plugin can easily say "I > need version X of plugingem Foo" even though the latest version of Foo > is X+2. > -- > Cheers! > - Pratik > http://m.onkey.org > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
