rake gems:unpack:dependencies and Rails

[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?

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

Thanks,

--Matt Jones


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.
To post to this group, send email to rubyonrails-core@...
To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

[Michael Koziarski]

On Sun, Sep 28, 2008 at 8:32 AM, Matt Jones <al2o3cr@...> wrote:
>
> 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?

> (see also http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1123
>  )
>
> Thanks,
>
> --Matt Jones
>
>
> >
>

--
Cheers

Koz

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.
To post to this group, send email to rubyonrails-core@...
To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---