From owner-freebsd-questions@freebsd.org  Sat Apr 16 16:06:53 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@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 46C6FB10473
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Sat, 16 Apr 2016 16:06:53 +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 170BA1FCC
 for <freebsd-questions@freebsd.org>; Sat, 16 Apr 2016 16:06:52 +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 u3GG6f2I068304
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Sat, 16 Apr 2016 10:06:41 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3GG6eZo068301;
 Sat, 16 Apr 2016 10:06:40 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Date: Sat, 16 Apr 2016 10:06:40 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: Polytropon <freebsd@edvax.de>
cc: JosC <bsduser@cloudzeeland.nl>,
 FreeBSD Questions <freebsd-questions@freebsd.org>
Subject: Re: Ports upgrade script
In-Reply-To: <20160416172045.8010cc7b.freebsd@edvax.de>
Message-ID: <alpine.BSF.2.20.1604161004330.46192@wonkity.com>
References: <2daca22c-7719-0776-fbe8-3c37021298bf@cloudzeeland.nl>
 <CAA2O=b9kHNz-q8NP_txAveRRw57jLWg8yMnTZvcQm0F4M98hOA@mail.gmail.com>
 <2e223983-d2ff-fd97-caba-732fd92aa20b@cloudzeeland.nl>
 <20160416172045.8010cc7b.freebsd@edvax.de>
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.4.3
 (wonkity.com [127.0.0.1]); Sat, 16 Apr 2016 10:06:41 -0600 (MDT)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Apr 2016 16:06:53 -0000

On Sat, 16 Apr 2016, Polytropon wrote:

> On Sat, 16 Apr 2016 16:34:16 +0200, JosC wrote:
>>
>> In een bericht van 16-4-2016 12:18:
>>>
>>> Portsnap isn't compatible with svn.
>>>
>> So I think I should revise the way I update my ports.
>> What I did with my 9.3 BSD was the following script (which worked
>> perfectly):
>>
>> !/bin/sh
>> cd /local/user/etc
>> svn update /usr/src
>> svn update /usr/ports
>> #
>> cd /usr/ports
>> make fetchindex
>> portsdb -fu
>> #
>> #
>> cd /usr/local/etc
>> portupgrade -na

Just adding: expect breakage if you do not routinely check 
/usr/ports/UPDATING before throwing portupgrade -a or portmaster -a at 
the new ports.

The ports team has really improved the situation, but once in a while 
there are still manual steps that must be taken before doing a mass 
upgrade of ports.

See http://www.wonkity.com/~wblock/docs/html/portupgrade.html for more 
detail.