/usr/ports/lang/ruby
bsd at perimeter.co.za
bsd at perimeter.co.za
Fri Aug 8 02:36:29 PDT 2003
Kris Kennaway writes:
> On Fri, Aug 08, 2003 at 10:51:59AM +0200, bsd at perimeter.co.za wrote:
>> Hi all.
>>
>> In my cvsup of the ports tree last night the ruby port went bye-bye.
>
> Sort of. It moved locations (see the MOVED file).
>
>> There are other ports which require it, most notably portupgrade.
>
> No, portupgrade now depends on ruby16 (or ruby18 on some
> architectures). There was however one port that was missed in the
> change-over, which is currently causing INDEX builds to fail. I
> expect that to get fixed as soon as knu wakes up :)
>
> Kris
Thanks for your quick response Kris.
OK, looking at /usr/ports/MOVED, I see a number of ruby* pieces have been
moved.
Is there an easy/correct method to use to migrate to a moved/renamed port.
And I'm curious about dependencies. For example, portupgrade's own version
has not changed, and 'pkg_info -r portupgrade*' still shows
ruby-1.6.8.2003.04.19 as required.
My guess would be:
1) pkg_delete ruby-1.6.8.2003.04.19
2) cd /usr/ports/lang/ruby16 (or ruby18?)
3) make install
But I could be way wrong here... :)
Regards,
Patrick.
More information about the freebsd-questions
mailing list