From owner-freebsd-ports@freebsd.org  Thu Feb 16 18:43:00 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6E57CE2EF1
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Thu, 16 Feb 2017 18:43:00 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "wonkity.com", Issuer "wonkity.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id BBB0E13DC
 for <freebsd-ports@freebsd.org>; Thu, 16 Feb 2017 18:43:00 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.15.2/8.15.2) with ESMTPS id v1GIgx0S043405
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Thu, 16 Feb 2017 11:42:59 -0700 (MST)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id v1GIgw7L043402;
 Thu, 16 Feb 2017 11:42:59 -0700 (MST)
 (envelope-from wblock@wonkity.com)
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
In-Reply-To: <alpine.BSF.2.20.1702121349541.46495@aneurin.horsfall.org>
Message-ID: <alpine.BSF.2.20.1702161141540.8741@wonkity.com>
References: <alpine.BSF.2.20.1702121349541.46495@aneurin.horsfall.org>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2
 (wonkity.com [127.0.0.1]); Thu, 16 Feb 2017 11:42:59 -0700 (MST)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 18:43:01 -0000

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.