rake gems:unpack:dependencies and Rails

rubyonrails-core
1

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 #1123 gems:unpack:dependencies attempting to unpack Rails gems - Ruby on Rails - rails   )

Thanks,

--Matt Jones

2

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?