From owner-freebsd-questions Mon Oct 7 17:52:48 2002 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 8650E37B401 for ; Mon, 7 Oct 2002 17:52:47 -0700 (PDT) Received: from badboy.mail.pas.earthlink.net (badboy.mail.pas.earthlink.net [207.217.120.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id E129243E42 for ; Mon, 7 Oct 2002 17:52:46 -0700 (PDT) (envelope-from parv_fm@mailsent.net) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by badboy.mail.pas.earthlink.net (8.11.6+Sun/8.11.6) with ESMTP id g97Nm0E21289 for ; Mon, 7 Oct 2002 16:48:00 -0700 (PDT) Received: from sdn-ap-007dcwashp0493.dialsprint.net ([63.188.65.239] helo=moo.holy.cow) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17yhZG-0000tT-00; Mon, 07 Oct 2002 16:45:43 -0700 Received: by moo.holy.cow (Postfix, from userid 1001) id 062FEAB12; Mon, 7 Oct 2002 19:48:20 -0400 (EDT) Date: Mon, 7 Oct 2002 19:48:20 -0400 From: parv To: Kevin Oberman Cc: questions@FreeBSD.ORG Subject: Re: Proper way to upgrade packaes from ports Message-ID: <20021007234820.GA78924@moo.holy.cow> Mail-Followup-To: Kevin Oberman , questions@FreeBSD.ORG References: <001301c26e4f$737ba530$6501a8c0@antichrist> <20021007223945.03BFB5D04@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021007223945.03BFB5D04@ptavv.es.net> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG in message <20021007223945.03BFB5D04@ptavv.es.net>, wrote Kevin Oberman thusly... > > The biggest down-side is the requirement that I run portsdb -Uu to > update the databases after a cvsup of the ports tree. This is a pretty > CPU intensive operation and can take a while on an older system. as i understand portsupgrade, "portsdb -U" would create the the index as if you had typed "make index" in your ports ($PORTSDIR). if you don't have the INDEX reflecting the current ports tree, things may go out of hand. such making of INDEX is part of freebsd ports (not portsupgrade). actually, after INDEX is made, "portsdb -u" finishes lighting fast ... in comparison. for me, creating the INDEX takes less time than updating it cvsup over a dialup connection. i don't have problem w/ the creation process being CPU intensive; bottleneck on my system is heavy disk activity. - parv -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message