What about the native code issue? Are you going to create a sub-directory per platform?
Also, the idea of specifying dependencies (ala Maven) in yaml sounds pretty cool. Were you thinking about doing something like that? Ben Josh Peek wrote: > Just trying to raise some awareness and discussion on a patch I > recently posted. > > The idea of freezing gems in your rails app has been around for a long > time. However there is no suggested convention to follow. Chris > Wanstrath has suggested the directory "vendor/gems" to be use in his > post "Vendor Everything" (http://errtheblog.com/post/2120). > > Once you set your path to this directory, everything works great. > There is no code difference between loading gems from your local > machine with rubygems or from the "vendor/gems" directory. > > If everyone is down with this convention, we should add a few things > in rails to encourage it. > > 1. Make the "vendor/gems" directory when you run the rails command. > 2. Add "vendor/gems" to the load path > 3. Load tasks from "vendor/gems" (I don't really use this but Nic > Williams finds it useful) > 4. Add some rake tasks to help you freeze gems. > > Are there any other techniques out there that work well for you? Or > does this sound like a delicious patch? > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
