Date: Wed, 6 Mar 2013 17:59:19 -0500 (EST) From: "Lawrence K. Chen, P.Eng." <lkchen@ksu.edu> To: Chris Rees <crees@FreeBSD.org> Cc: FreeBSD Ports <ports@freebsd.org> Subject: Re: portdowngrade(CVS) deprecated -> alternative for portsnap(8) usage Message-ID: <1067072446.23381912.1362610759524.JavaMail.root@k-state.edu> In-Reply-To: <CADLo83-P6yLtTLhQ8kn1yynk-xEDiTmaMHLv4CgSpAK8WVuZ_Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- > On 6 March 2013 21:32, Lawrence K. Chen, P.Eng. <lkchen@ksu.edu> > wrote: > > Doesn't the old advice of adding, something like > > > > REFUSE audio/oss > > > > to /etc/portsnap.conf still work? > > I hope I haven't upset anyone with the change in behaviour, but I > need > to reiterate that portdowngrade no longer touches the ports tree-- it > simply provides a port skeleton in the current directory. > > Therefore, this is no longer a problem. > > Chris > Except I don't know of another way to downgrade a port to work with other ports....perhaps there's a way in portmaster.rc that I haven't stumbled upon yet. I know I had something in pkgtools.conf at one time to prevent virtualbox from upgrading (has istgt been updated to work with the current virtualbox yet? Have since removed istgt....) Forget what the other time that I used portdowngrade....something to do with X11 I think, which was resolved by rebuilding with "WITH_NEW_XORG=YES" in my /etc/make.conf. OTOH, there are parts of my ports tree that I have to remember to 'update' after a 'portsnap update'....like www/chromium Lawrence
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1067072446.23381912.1362610759524.JavaMail.root>