Re: /usr/ports/lang/ruby
Kris Kennaway writes: 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. Yes, as it should. The port has not been upgraded, it has only moved location. The next time it is upgraded, portupgrade will follow the entry in the MOVED file to the new location, and everything will continue to be just fine :) Kris Aaahh! - she be very pretty! OK - so I should learn a little patience (like my mother always told me - something about a virtue.) and in due course the tango will be completed. Thanks for taking the time out for me Kris. Regards, Patrick. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/ports/lang/ruby
Kris Kennaway writes: On Fri, Aug 08, 2003 at 10:51:59AM +0200, [EMAIL PROTECTED] 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/ports/lang/ruby
On Fri, Aug 08, 2003 at 10:51:59AM +0200, [EMAIL PROTECTED] 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 pgp0.pgp Description: PGP signature
/usr/ports/lang/ruby
Hi all. In my cvsup of the ports tree last night the ruby port went bye-bye. There are other ports which require it, most notably portupgrade. Of course, the pre-existing ruby is still installed, but I'm a bit confused about what the plans are, because right now portupgrade cannot even upgrade the ports it requires for itself Where should I go to find out what the plans are going forward, and how to keep my system ports current. Thanks, Patrick. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
