From owner-freebsd-questions@FreeBSD.ORG Tue Dec 28 19:31:41 2004 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 6128B16A4CE for ; Tue, 28 Dec 2004 19:31:41 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7FCD43D2D for ; Tue, 28 Dec 2004 19:31:40 +0000 (GMT) (envelope-from reso3w83@verizon.net) Received: from ringworm.mechee.com ([4.26.84.7]) by out001.verizon.net ESMTP <20041228193140.TZBL28025.out001.verizon.net@ringworm.mechee.com>; Tue, 28 Dec 2004 13:31:40 -0600 Received: by ringworm.mechee.com (Postfix, from userid 1001) id 728D52CE743; Tue, 28 Dec 2004 11:28:46 -0800 (PST) From: "Michael C. Shultz" To: freebsd-questions@freebsd.org User-Agent: KMail/1.7.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Date: Tue, 28 Dec 2004 11:28:45 -0800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412281128.46165.reso3w83@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [4.26.84.7] at Tue, 28 Dec 2004 13:31:39 -0600 cc: ringworm@inbox.lv Subject: Re: portupgrade vs. portmanager X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 19:31:41 -0000 On Tuesday 28 December 2004 10:03 am, you wrote: > Does portmanager handle packages? If not any plans to do so? I would > be happy to help with testing. portmanager only handles packages in that it builds back up packages of each port it updates, these packages are correctly build for your specific system. The problem with packages that you down load is they have to be built for the lowest common denominator, ie. lowest cpu that most are likely to have (486?, 586?), no options, etc, and they are usually built with out of date dependencies. As a test, install a package not allready on your system with a lot of dependencies like misc/sword for example then run portmanager. You'll see portmanager find everything about that package that is wrong for your system and then correct it, and it will also end up rebuilding misc/sword and making a new package of it. That new package will be built correctly for your system. After you are familiar with how portmanager works and if you still want to help with testing then yes I am very interested, please let me know. -Mike > > On Sat, 25 Dec 2004, Michael C. Shultz wrote: > > > > Portupgrade has one serious flaw in my opinion and that is > > > > running something like pkgdb -F damages the port installation > > > > database as far as I'm concerned. It causes the data base to > > > > say ports were built with dependency ports that they were > > > > never really built with. Portmanager only addresses that one > > > > issue and for the forseeable future that is where all the focus > > > > will be, only on correctly updating ports.