Date: Fri, 1 Nov 2013 20:19:16 +0100 From: Torfinn Ingolfsen <tingox@gmail.com> To: FreeBSD Ports ML <freebsd-ports@freebsd.org> Cc: Chris Rees <crees@FreeBSD.org> Subject: Re: portdowngrade(CVS) deprecated -> alternative for portsnap(8) usage Message-ID: <CAJ_iqtap5iehvROddgXMzQ95t4VSHD-4UdBDk%2BGCjVp%2Br_i2bg@mail.gmail.com> In-Reply-To: <CADLo83_cCe_rW=i8znMVm9RyZPCZ46zXAznrQ45e9%2B1sLmzSUA@mail.gmail.com> References: <20130104.195945.545.13@DOMY-PC> <CADLo83-eZaBMhxsFYyxj9-=PvUyqkZpGWHhE1Pnb_G=R8hOtZA@mail.gmail.com> <20130306.191546.824.1@DOMY-PC> <CADLo83_cCe_rW=i8znMVm9RyZPCZ46zXAznrQ45e9%2B1sLmzSUA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 6, 2013 at 9:00 PM, Chris Rees <utisoft@gmail.com> wrote: > > Portdowngrade now simply checks out the port to your current directory; if > you run it in ~, you simply cd $portname. > I got bitten by this change today. I think portdowngrade should warn users that it will work on the current directory, not the port directory. Something like: "NOTE: this program will check out the new port into a directory named $portname in your current directory." HTH -- Regards, Torfinn Ingolfsen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ_iqtap5iehvROddgXMzQ95t4VSHD-4UdBDk%2BGCjVp%2Br_i2bg>