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 dep
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, por
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
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 upgra
On Fri, Aug 08, 2003 at 11:36:23AM +0200, [EMAIL PROTECTED] 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, portupgrad
