[csw-pkgsubmissions] newpkgs ruby19, ruby19dev, ruby19ri, ruby19sa(...)

[Philip Brown]

On Mon, Apr 19, 2010 at 7:56 PM, Ben Walton <bwalton at opencsw.org> wrote:
>
>> So... we COULD replace all our "CSWruby*" packages, with "empty"
>> packages that depend on ruby18 packages(that you would then have to
>> make)... but only as a temporary stopgap measure. The packages need
>> to clearly identify that they are a transition package only.  There
>> will be no ongoing "CSWruby" package, after transition is complete.
>
> I think this will need to get tied into the system with alternatives
> too, so that we can setup /opt/csw/bin/ruby -> ruby18, etc.  I'll also
> need to handle migrating gems for the ruby18 packages since the
> $libdir will change when I add a suffix to everything.

Hrrrm.

well, you probably shouldnt use CSWalternatives, until I finally come
out with the newer version that is NFS friendly. (probably a week).
initial proof-of-concept code is written,but I have to get around to
packaging it. ugh.


Hmm... i was presuming that the "alternatives" call would be in the
CSWruby virtual package,but it would actually go in the individual
"real", versioned ruby packages, I think.
That makes sense to me.