From owner-freebsd-questions@FreeBSD.ORG Fri Aug 21 19:02:42 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAF981065692 for ; Fri, 21 Aug 2009 19:02:42 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 4AA218FC1A for ; Fri, 21 Aug 2009 19:02:41 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1MeZNn-0002LW-Pu for freebsd-questions@freebsd.org; Fri, 21 Aug 2009 21:02:39 +0200 Received: from pool-70-21-10-24.res.east.verizon.net ([70.21.10.24]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Aug 2009 21:02:39 +0200 Received: from nightrecon by pool-70-21-10-24.res.east.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Aug 2009 21:02:39 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Followup-To: gmane.os.freebsd.questions Date: Fri, 21 Aug 2009 15:02:41 -0400 Lines: 51 Message-ID: References: <4A8DD867.9020604@videotron.ca> <1250812091.28087.23.camel@lholcombe-desktop> <4A8ED2D5.30808@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-70-21-10-24.res.east.verizon.net Sender: news Subject: Re: installation sequence X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nightrecon@hotmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Aug 2009 19:02:42 -0000 PJ wrote: [snip] > > Ok, I normally do something like that... problem here was that I made > the mistake of thinking that an interesting little script I found was > good for updating... but, I was sadly mistaken. The error was due to a > badly downloaded ports tree. That fixed, all works fine. > I really only have problems when some extraneous garbage comes along and > I'm suckere in to try it. > Here's the script (I modified it and it seems to work just fine) but I > sure would like to hear if that makes sense. > I called it update.ports and it runs from any directory. It can be > changed to update source and docs if so desired or all could be done > from same script. Let me know, please, if it's ok? > ====== > #!/bin/sh > # > # Update source, docs and ports > > LOCAL_DIR="$(pwd)" > > cd /usr/share/examples/cvsup > csup ports-supfile > cd /usr/ports > make fetchindex > > /usr/local/sbin/portsdb -u > /usr//local/sbin/pkgdb -uvF > > cd $LOCAL_DIR > ======= > I essentially do something very similar. About once a week I do this: csup -L 2 ports && portsdb -uF && pkgdb -u && portversion This pretty much does the same thing as the script. I keep intending to make it a cron job and email me the output, but until I get 'round to it I just take a quick gander at the output and if needed issue a portupgrade -a. 9.8 times out of 10 this is all I ever need. Every once in a while I have to manually fix something, but that isn't all that often, maybe once or twice a year. Another thing is to read UPDATING religiously as this can help sidestep boo boos before they happen. [snip] -Mike