From owner-freebsd-questions@freebsd.org Sat Apr 16 15:20:48 2016 Return-Path: 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 9F759B1010A for ; Sat, 16 Apr 2016 15:20:48 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 67CD8185F for ; Sat, 16 Apr 2016 15:20:48 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-71-243.dynamic.qsc.de [92.195.71.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 301CB27650; Sat, 16 Apr 2016 17:20:46 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u3GFKjXN002825; Sat, 16 Apr 2016 17:20:45 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 16 Apr 2016 17:20:45 +0200 From: Polytropon To: JosC Cc: FreeBSD Questions Subject: Re: Ports upgrade script Message-Id: <20160416172045.8010cc7b.freebsd@edvax.de> In-Reply-To: <2e223983-d2ff-fd97-caba-732fd92aa20b@cloudzeeland.nl> References: <2daca22c-7719-0776-fbe8-3c37021298bf@cloudzeeland.nl> <2e223983-d2ff-fd97-caba-732fd92aa20b@cloudzeeland.nl> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2016 15:20:48 -0000 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 > # > > So this part I replaced now with: > > portsnap fetch update > > kind of lost how to continue now... Your script does _more_ than just update installed ports. It also updates the OS sources, but it does _not_ upgrade the OS according to those sources. If that's what you intend, try the following: #!/bin/sh # update OS sources svn update /usr/src # update ports tree svn update /usr/ports make fetchindex portsdb -fu # upgrade all installed ports portupgrade -na You can exchange # update ports tree svn update /usr/ports with the following: # update ports tree portsnap fetch extract But you should keep _one_ of those two methods. It's usually wise to start with an empty /usr/ports directory and have the desired tool populate it for the first time, then apply changes on further runs. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...