From owner-freebsd-questions Fri Dec 20 19:26:59 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 E00E837B401 for ; Fri, 20 Dec 2002 19:26:57 -0800 (PST) Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CB7A43EE5 for ; Fri, 20 Dec 2002 19:26:57 -0800 (PST) (envelope-from deepbsd@yahoo.com) Received: from user-119a2km.biz.mindspring.com ([66.149.10.150] helo=sylvester.dsj.net) by hawk.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18PaHw-0007WH-00; Fri, 20 Dec 2002 19:26:56 -0800 Received: from sylvester.dsj.net (dsj@localhost [127.0.0.1]) by sylvester.dsj.net (8.12.3/8.12.3/Debian -4) with ESMTP id gBL3QsK4029992; Fri, 20 Dec 2002 22:26:55 -0500 Received: (from dsj@localhost) by sylvester.dsj.net (8.12.3/8.12.3/Debian -4) id gBL3QrnE029991; Fri, 20 Dec 2002 22:26:53 -0500 X-Authentication-Warning: sylvester.dsj.net: dsj set sender to deepbsd@yahoo.com using -f Date: Fri, 20 Dec 2002 22:26:53 -0500 From: "David S. Jackson" To: Daniel Schrock Cc: freebsd-questions@FreeBSD.ORG, Shane Kinney Subject: Re: problem with installing new ports Message-ID: <20021221032653.GJ17554@sylvester.dsj.net> Reply-To: "David S. Jackson" References: <3E039A00.4050107@speakeasy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E039A00.4050107@speakeasy.net> User-Agent: Mutt/1.4i 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 On Fri, Dec 20, 2002 at 04:30:24PM -0600 Daniel Schrock wrote: > well... if your package db has gotten way out of sync with your ports > collection, it creates a nightmare that only time and effort will fix. > You have a couple options, both equally suck, but have their merits as well. > > option 1: find the new dependancies or delete the dependancy if it no > longer exists... once completed, use `portversion -l '<'` to see which > installed ports have newer versions available. use portupgrade to get > them current. takes forever but usually works...just be careful when > changing dependancies, > > option 2: remove as many old ports as possible, especically if they are > not used/needed much and get your collection down to a small level, then > move up to option 1. This method is easier, but not necessarily an > option on many systems. its nice for workstations and cleaning the > system out, not so good if a production box that requires all ports that > are installed... > > once pkgdb -F can be run without errors, cvsup, use `portsdb -Uu` then > check for old ports using `portversion -l '<'`. > > from this point on, you should have a clean system. to keep it clean, > either always run pkgdb -F after installing a port, or always use > `portinstall -N` to install your ports, which will update pkgdb on its > own... > > portupgrade is pretty much an all or nothing port... if you use it > religiously, its great... if you forget about it, its a hassle later on > down the road. > > its a great port but works best on fresh installs... its a little harder > to deal with if you have already installed a lot of ports. This has been one of the most helpful and practical pieces of advice I have ever gotten from this terrific list. Thank You! I'll start planning this operation. (Option 2 first, then Option 1.) (The portsdb is really still a mystery to me, and after letting it get so far out of synch as it is, I hope that I too can have a clean system again without reinstalling from scratch!) The advice above seems so good that I didn't trim it; I hope someone else can get as much help out of it as I have and therefore felt it's worth leaving intact. :-) -- David S. Jackson dsj@dsj.net =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Life is divided into the horrible and the miserable. -- Woody Allen, "Annie Hall" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message