ruby_select plan, rubygem: dependency operator

[C. Florian Ebeling]

On Wed, Apr 15, 2009 at 11:19 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
>
> On Apr 15, 2009, at 03:03, C. Florian Ebeling wrote:
>
>> A ruby port also consists of only 3 or 4 lines of effective code, if you
>> use
>> the ruby.setup call from the ruby group file. What worries me more is
>> the brittleness when you just can pull away dependencies using the
>> special package manager, gem in the ruby case.
>
> Yes, it would be good to fix it so that users cannot cause that problem.

I don't see what the correct behaviour is, when having a port that wraps
over a gem, for instance. When the gem is loadable as ruby library, then
it is visible to the gem manager, and can be removed as well. Even if
there was a way to make a gem visible but not manipulatable, that would
be very strange behaviour from a ruby/gem perspective.

So I suggest not trying to stay in control here, but rather act like for
other dependencies for which we don't exert control (path, lib).

Or do you have an idea how to really fix this problem?





-- 
Florian Ebeling
Twitter: febeling
florian.ebeling at gmail.com