From owner-freebsd-questions@FreeBSD.ORG Sat Dec 25 18:16:21 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 144E916A4CE for ; Sat, 25 Dec 2004 18:16:21 +0000 (GMT) Received: from out007.verizon.net (out007pub.verizon.net [206.46.170.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74A7543D1D for ; Sat, 25 Dec 2004 18:16:20 +0000 (GMT) (envelope-from reso3w83@verizon.net) Received: from ringworm.mechee.com ([4.26.84.7]) by out007.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041225181619.IEDH27681.out007.verizon.net@ringworm.mechee.com> for ; Sat, 25 Dec 2004 12:16:19 -0600 Received: by ringworm.mechee.com (Postfix, from userid 1001) id 5FEFB2CE740; Sat, 25 Dec 2004 10:13:27 -0800 (PST) From: "Michael C. Shultz" To: freebsd-questions@freebsd.org Date: Sat, 25 Dec 2004 10:13:25 -0800 User-Agent: KMail/1.7.2 References: <41CBB0D6.6080807@att.net> <200412241731.14458.reso3w83@verizon.net> <20041225125311.GA43679@scode-whitestar.mine.nu> In-Reply-To: <20041225125311.GA43679@scode-whitestar.mine.nu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412251013.26800.reso3w83@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out007.verizon.net from [4.26.84.7] at Sat, 25 Dec 2004 12:16:19 -0600 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: Sat, 25 Dec 2004 18:16:21 -0000 On Saturday 25 December 2004 04:53 am, Peter Schuller wrote: > > Right now portmanager is upgrading kdelibs and I'm still using it. > > The only problem that might occur is between the > > deinstall/reinstall steps I'll be missing the libraries for about a > > minute, when this happens I just wait untill its finished > > reinstalling then continue. > > Here is a recap of what happens: > > ... > > > I've been testing this for a year now and haven't had a problem yet > > using a program while it is being updated. > > That does indeed sound perfectly painless. I failed to remember that > there is another factor playing into my annoyance with pkg_chk - > namely that it seems to remove dependent packages in chunks prior to > re-installing them. So the end-result is that the system is > completely missing several packages for extended periods of time > while a bunch of other packages are being compiled. > > I don't know why this is done or exactly under what circumstances. > But indeed, the way portmanager behaves as you described above sounds > a lot better. > > > 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. > > Ok. That sounds good. To be honest I have never understood why the > dependencies seem to randombly break, requiring a lot of fiddling > with pkgdb. > > I tried portmanager in the past but missed the fact of 'proper' > upgrading of entire dependency chains. I will have another go now > though. Thanks for the clarifications! Thanks for giving portmanager a try! Right now it is having a problem with conflicting ports (like some of the linux base ports) where portupgrade can alter the dependencies portmanager gets a little confused so you have to resolve the conflicts manually. That should be resolved in portmanager ver 0.2.2. -Mike manually if they occur.