Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Automatically invoke Update task after freezing to gems

#1623

The rails:freeze:edge task will automatically invoke rails:update, but rails:freeze:gems does not.

This patch calls rails:update at the end of rails:freeze:gems, to make sure that scripts are in sync with the newly-frozen version of rails.

Motivated by the fact that I got into trouble after freezing to a previous version of Rails, but I forgot the manual step of running rake rails:update and things went a bit haywire for a while until I figured it out.

Reported by Jeff Cohen · December 23rd, 2008 @ 10:04 PM

State: invalid
Milestone: 2.x
Assigned to: Pratik Pratik
Importance: none

Activity

  1. Ben Reubenstein
  2. Brian Hogan
    Brian Hogan

    +1

    It may not be necessary but it's inconsistent and that's what bugs me.

    December 31st, 2008 @ 04:30 AM

  3. Pratik
    Pratik
    • Assigned user set to Pratik
    • State changed from new to invalid

    I don't think this makes much sense. When you run rails:freeze:edge, you're updating the rails itself. But when you rails:freeze:gems, you're not really updating Rails. rails:freeze:gems will/should update frozen rails gems only if you manually change RAILS_GEM_VERSION in env.rb. But that process is irrelevant to rails:freeze:gems and the processes of freezing/upgrading Rails shouldn't be mixed in case of freezing gems.

    Thanks.

    March 8th, 2009 @ 12:50 AM