From owner-freebsd-questions@FreeBSD.ORG Wed Oct 8 13:23:24 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3239C16A4B3 for ; Wed, 8 Oct 2003 13:23:24 -0700 (PDT) Received: from firecrest.mail.pas.earthlink.net (firecrest.mail.pas.earthlink.net [207.217.121.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3923643F3F for ; Wed, 8 Oct 2003 13:23:22 -0700 (PDT) (envelope-from richardcoleman@mindspring.com) Received: from c-24-98-233-138.atl.client2.attbi.com ([24.98.233.138] helo=mindspring.com) by firecrest.mail.pas.earthlink.net with asmtp (Exim 3.33 #1) id 1A7Kq6-0005dP-00; Wed, 08 Oct 2003 13:23:18 -0700 Message-ID: <3F847243.1090201@mindspring.com> Date: Wed, 08 Oct 2003 16:23:31 -0400 From: Richard Coleman Organization: Critical Magic, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David.Bear@asu.edu References: <20031008113325.B11482@asu.edu> In-Reply-To: <20031008113325.B11482@asu.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 1ee258965991efcb0865379cdb43356e5e89bb4777695beb702e37df12b9c9efd18280c42a5fea5cdab6140092ed2179350badd9bab72f9c350badd9bab72f9c cc: freebsd-questions@freebsd.org Subject: Re: cvsup and portupgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: richardcoleman@mindspring.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Oct 2003 20:23:24 -0000 David Bear wrote: > I'm still trying to muddle through the loads of different ways to keep > FreeBSD 'current' -- meaning, safely patched, aka RELENG_5_1 (for me) > > As I conceptualize the operations there are two levels of 'patching', > 1) the kernel and base system > 2) then all the ports that I may have installed > > I've read the cvsup docs and can see how to update both the kernel > source and ports. But the problem I see is the ports. After the > ports collection has cvsupdated, I would still need to do a make > install for each port I have previous installed, correct? (or, more > appropriately, make deinstall, the cvsup the ports, then make install) > Is this making things more difficult? Seems there really should be a > cleaner way to keep things updated. > > I've heard reference to a portupgrade package, but can't find any > details on how and what it really does-- and how well it plays with > cvsupdate. > > The other rotten thing here is that cvsupdate requires modula-3 -- and > portupgrade requires ruby... It would really be nice if all this were > done in the most perfect language, python;-) > > looking for some advice.. thx. cvsup and portupgrade do different things. Cvsup will keep your copy of a particular source trees (/usr/src, /usr/port, etc.) up-to-date with the current sources in the CVS repository. Actually, cvsup can track the sources along any CVS branch point or by date. There is usually a pre-built binary package for cvsup, so you don't generally need to build it from source (or build the modula3 package). Just get it from the FreeBSD ftp site and use pkg_add to add the binary package. But once you've got the updated sources, you need to update your machine. For /usr/src, you have to follow the procedures to "build the world" Check the handbook for this. For /usr/port, you can update manually (pkg_delete the old version and make install the new version) or use portupgrade. To get started with portupgrade, just do: cd /usr/ports/sysutils/portupgrade make install clean rehash # if you are using csh or tcsh pkgdb -F portsdb -Uu If you want to see the ports that are available for updating, use the command "portversion". You will need to re-run "portsdb -Uu" every time you update the ports source tree using cvsup. Richard Coleman richardcoleman@mindspring.com