rake gems:unpack:dependencies and Rails

When a gem depends on Rails and gems:unpack:dependencies is called, the
current code tries to unpack Rails into vendor/gems. Should there be a
special
case to detect and/or prevent this?

(see also http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1123
  )

Thanks,

--Matt Jones

When a gem depends on Rails and gems:unpack:dependencies is called, the
current code tries to unpack Rails into vendor/gems. Should there be a
special
case to detect and/or prevent this?

I don't really use gems and unpacking so I'm the wrong person to make
the call on what's 'surprising' or not. but it certainly does seem
like a special case detecting 'rails' and using the freeze:gems code
would at least be less surprising. But I'm not sure if that's what
people truly want or expect.

Does anyone who uses config.gems and unpacking have a strong opinion?