Date: Fri, 8 Aug 2003 02:42:20 -0700 From: Kris Kennaway <kris@obsecurity.org> To: bsd@perimeter.co.za Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: /usr/ports/lang/ruby Message-ID: <20030808094220.GA98568@rot13.obsecurity.org> In-Reply-To: <courier.3F336F17.00000B91@perimeter.co.za> References: <courier.3F3364AF.000004AB@perimeter.co.za> <20030808091546.GA98440@rot13.obsecurity.org> <courier.3F336F17.00000B91@perimeter.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Fri, Aug 08, 2003 at 11:36:23AM +0200, bsd@perimeter.co.za wrote: > 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. 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/M3B7Wry0BWjoQKURAudPAKCEy1QEnL+xqsmGIF7dD0zaU9wHGACdEulX IRO3nPOvTncvZ08Zb5xI6Z4= =OMKN -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030808094220.GA98568>