Date: Thu, 16 Feb 2017 11:42:58 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Dave Horsfall <dave@horsfall.org> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Question on upgrading ports after 9.3->10.3 Message-ID: <alpine.BSF.2.20.1702161141540.8741@wonkity.com> In-Reply-To: <alpine.BSF.2.20.1702121349541.46495@aneurin.horsfall.org> References: <alpine.BSF.2.20.1702121349541.46495@aneurin.horsfall.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 12 Feb 2017, Dave Horsfall wrote: > Me again :-) I finally got around to following the notes that David > Wolfskill kindly provided (thanks!) and apart from some oddity about > "httpd" requiring a missing "libdb-4.2.so.2" (which will get rebuilt > anyway), I'm a bit wary of this: > > 7. Back up any files in /usr/local that you wish to save [...] > 8. Manually check /usr/local [...] to make sure that they are really > empty. > > Errm, why? Is it going to clean out /usr/local from under my feet? If > so, then that's a bit rude... Because of disk space limitations, I've got > /usr/ports -> /usr/local/ports (/usr/local is a separate file system). > And then there's all my private stuff... I think it means "save any local > configuration files etc"; if so, it could be better phrased. Presumably, the idea is to start from a blank slate. No, portmaster does not delete those directories. > PS: For those who also have a Mac, do *not* futz around with symlinks in > this manner, as it confuses the hell out of macports... It can be a problem on FreeBSD also.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1702161141540.8741>