Date: Sun, 15 Jan 2012 17:42:48 -0500 From: Daniel Staal <DStaal@usa.net> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: Portmanager Status Report Gone Message-ID: <BFFA6EB3451D9E14A2F76B84@mac-pro.magehandbook.com> In-Reply-To: <20120115153520.62812867@scorpio> References: <40F552CF734E955EB7878763@mac-pro.magehandbook.com> <20120115103332.09d5f2ca@scorpio> <329BBA85301E2290BF6E0570@mac-pro.magehandbook.com> <20120115122547.0b71e16c@scorpio> <18121B8E00E7690C5FB44C5C@mac-pro.magehandbook.com> <20120115153520.62812867@scorpio>
next in thread | previous in thread | raw e-mail | index | archive | help
--As of January 15, 2012 3:35:20 PM -0500, Jerry is alleged to have said: > You don't have to manually erase the tree. I believe that: > > "portsnap fetch extract" > > is all you need to do to replace the ports tree with a fresh copy. It > won't hurt anything since it doesn't touch the configuration files. --As for the rest, it is mine. Done, and it didn't fix my problem. Something's obviously gone seriously weird with my system. What would happen if I did blow away the config files? What's the minimum necessary for my system to be able to manage it's ports collection? I really don't want to reinstall from scratch over this (If nothing else, it's my main fileserver. I've got backups, but that would take ages.), but I'm thinking rebuilding my ports database from bare bones sounds like it might be a good idea. Daniel T. Staal --------------------------------------------------------------- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BFFA6EB3451D9E14A2F76B84>