From owner-freebsd-questions@FreeBSD.ORG Mon Dec 27 02:03:56 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 CFAAA16A4CE for ; Mon, 27 Dec 2004 02:03:56 +0000 (GMT) Received: from fusion.vilot.net (vilot.com [64.246.32.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9629E43D45 for ; Mon, 27 Dec 2004 02:03:56 +0000 (GMT) (envelope-from tom@vilot.com) Received: from [192.168.1.102] (c-24-8-184-241.client.comcast.net [24.8.184.241]) (authenticated bits=0) by fusion.vilot.net (8.13.1/8.12.9) with ESMTP id iBR2155L021804; Sun, 26 Dec 2004 20:01:10 -0600 (CST) (envelope-from tom@vilot.com) Message-ID: <41CF6D85.6050704@vilot.com> Date: Sun, 26 Dec 2004 19:03:49 -0700 From: Tom Vilot User-Agent: Mozilla Thunderbird 1.0 (X11/20041222) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chuck Swiger References: <41CF5C95.8060702@vilot.com> <41CF69EA.6070002@mac.com> In-Reply-To: <41CF69EA.6070002@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: questions@freebsd.org Subject: Re: Oooooops: make deinstall 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: Mon, 27 Dec 2004 02:03:57 -0000 Chuck Swiger wrote: > > pkg_info, pkg_info -ag, pkg_info -ar (or pkg_info -aR, depending on > which way you want to see the dependencies). Those are very handy .... I guess, tho ... since make deinstall will "force remove" a package even if another package uses it, what I really want to do is something like: pkgdb -F ... see the first "failed" dependency ... .... go find the package and install it ... repeat. :c( Seems like the kind of thing that could be scripted .... > > If you created a /usr/ports/packages directory, portupgrade and such > will leave the precompiled binary packages you've created on your > system there. Ah! > > Otherwise, consult your backups. well, this isn't a production machine by any stretch .... so I didn't do backups :c)