On 29 Dec., 21:56, Evgeny <[email protected]> wrote: > As you probably know, Rails 2.2 has this really stupid way of handling > vendor/gems - it requires the directory to be named vendor/gems/haml-2.0.6 - > and that is just plain silly. And even more than that, it requires to > install the gem and then it somehow "copies" the installed gem into rails .. > or some other weird thing that it does. It's just crazy.
That sounds reasonable. But I must admit that I haven't been using vendor/gems at all. I prefer dependencies to keep the size of my project down. > I think my way is better, what I do is add the gems right into vendor/gems, > and then just checkout the correct tag (like 2.0.6) and submit that into my > own git. > > cd RAILS_ROOT > git add submodule git://github.com/nex3/haml.git vendor/gems/haml > cd vendor/gems/haml > git co -b 2.0.6 2.0.6 > #http://gist.github.com/41380as RAILS_ROOT/lib/rails_vendor_gems_ng.rb > cd RAILS_ROOT > git submodule update > git commit Unfortunately, I'm not using Git. I use Subversion. But thank you so much for you suggestion! :) Anyway, what about Rubyforge? config.gem 'haml', :version => '2.0.6', :source => "http:// gems.rubyforge.org/" -- David Trasbo. http://twitter.com/datra --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" 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/haml?hl=en -~----------~----~----~----~------~----~------~--~---
