Date: Wed, 6 Mar 2013 20:00:16 +0000 From: Chris Rees <utisoft@gmail.com> To: rank1seeker@gmail.com Cc: Chris Rees <crees@freebsd.org>, ports@freebsd.org Subject: Re: portdowngrade(CVS) deprecated -> alternative for portsnap(8) usage Message-ID: <CADLo83_cCe_rW=i8znMVm9RyZPCZ46zXAznrQ45e9%2B1sLmzSUA@mail.gmail.com> In-Reply-To: <20130306.191546.824.1@DOMY-PC> References: <20130104.195945.545.13@DOMY-PC> <CADLo83-eZaBMhxsFYyxj9-=PvUyqkZpGWHhE1Pnb_G=R8hOtZA@mail.gmail.com> <20130306.191546.824.1@DOMY-PC>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 Mar 2013 19:15, <rank1seeker@gmail.com> wrote: > > > > http://forums.freebsd.org/showthread.php?p=203241 > > > > > > Will it be transformed to checkout via SVN, only origins we need, or will > > > it be dumped from ports tree as obsolete. > > > Thanks. > > > > > > > Hey, > > > > I rewrote it in sh, quite simply because I thought that c++ was insane > > for such simple code. > > > > I'm afraid it doesn't quite have the same behaviour, but it's still > > very easy to use. > > > > Please let me know if there's something you desperately miss about the > > old version. > > > > Chris > > > > > Thanks for your effort! > > # portdowngrade audio/oss > Listed all revisions > # portdowngrade audio/oss r300895 > I've picked one from the past > > However: > # portsnap fetch update > Is blind to this change and fails to update it back, to it's latest version > > portdowngrade should also alter/update portsnap's DB Portdowngrade now simply checks out the port to your current directory; if you run it in ~, you simply cd $portname. I wouldn't recommend the old behaviour of downgrading in place like that; it significantly complicates many things, including svn conflicts and portsnap update maybe overwriting it, maybe not. I view it as a tool for testing older versions/reverting until a fix is issued. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83_cCe_rW=i8znMVm9RyZPCZ46zXAznrQ45e9%2B1sLmzSUA>