On 17 January 2011 15:51, Leonardo Mateo <[email protected]> wrote: > On Mon, Jan 17, 2011 at 11:38 AM, Colin Law <[email protected]> wrote: >> On 17 January 2011 14:28, Leonardo Mateo <[email protected]> wrote: >>> Hi guys, >>> I'm haviing problems when trying to freeze rails within my application. >>> By doing this: >>> rake rails:freeze:edge RELEASE=2.3.10 >> >> Why are you specifying edge, is that really what you want? > I've always frozen rails this way. I don't want to freeze all my gems > but only rails. > >> If rails is specified as 2.3.10 in environment.rb then you should just >> be able to do >> rake rails:freeze:gems >> or if you feel you need to specify the version >> rake rails:freeze:gems VERSION=2.3.10 >> note VERSION not RELEASE > Will this freeze gems under the vendor/gems and rails under vendor/rails?
Try it and see, it is some time since I last did it. If you don't like the result all you have to do is delete the files. All freeze does is to copy files. Also you have always got it committed to you source control system so you can easily get back to where you were. Colin Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
