From owner-freebsd-ports@FreeBSD.ORG Fri Oct 24 02:41:28 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 145701065681 for ; Fri, 24 Oct 2008 02:41:28 +0000 (UTC) (envelope-from joshua_rickmar@eumx.net) Received: from eumx.net (eumx.net [85.114.129.133]) by mx1.freebsd.org (Postfix) with ESMTP id A25E18FC17 for ; Fri, 24 Oct 2008 02:41:26 +0000 (UTC) (envelope-from joshua_rickmar@eumx.net) Received: from localhost ([127.0.0.1]:37631 helo=ssl.eumx.net) by eumx.net with esmtp (Exim 4.63) (envelope-from ) id 1KtCc8-0007PS-1v; Fri, 24 Oct 2008 02:41:24 +0000 Received: from 67.177.142.45 (SquirrelMail authenticated user joshua_rickmar) by ssl.eumx.net with HTTP; Thu, 23 Oct 2008 22:41:24 -0400 (EDT) Message-ID: <55557.67.177.142.45.1224816084.squirrel@ssl.eumx.net> In-Reply-To: <1224815453.1624.0.camel@wombat.2hip.net> References: <53980.67.177.142.45.1224810884.squirrel@ssl.eumx.net> <49012D63.8020201@math.missouri.edu> <61973.67.177.142.45.1224815151.squirrel@ssl.eumx.net> <1224815453.1624.0.camel@wombat.2hip.net> Date: Thu, 23 Oct 2008 22:41:24 -0400 (EDT) From: "Josh Rickmar" To: "Robert Noland" User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-ports@freebsd.org Subject: Re: Concern about using pkg_delete -r X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Oct 2008 02:41:28 -0000 On Thu, October 23, 2008 10:30 pm, Robert Noland wrote: > On Thu, 2008-10-23 at 22:25 -0400, Josh Rickmar wrote: > >> On Thu, October 23, 2008 10:05 pm, Stephen Montgomery-Smith wrote: >> >>> Josh Rickmar wrote: >>> >>> >>>> I'm hoping that this list covers port tools as well as the usual >>>> discussions about the actual ports. If not, please CC this to the >>>> proper list. >>>> >>>> I want to use pkg_delete to remove an installed port, but also want >>>> to remove its orphaned dependencies along with it. After looking at >>>> the pkg_delete(1) man page, the -r flag seems to be the option to >>>> use for this job. My concern, though, is about the wording: >>>> >>>>> In addition to specified packages, delete all >>>>> packages that depend on those packages as well. >>>> >>>> Does this mean that if I pkg_delete -r pkgA, than pkgB (a >>>> dependency) will be removed with it, even though it is dependency of >>>> pkgC? Or is pkg_delete (or pkg_deinstall) smart enough to >>>> understand this dependency and keep pkgB installed? >>>> >>>> If in this scenario pkgB would be deleted, should an extra warning >>>> be added to the man page so that users know that using this flag >>>> could potentially break their other ports? >>> >>> I think you have the dependency relationship the wrong way around. >>> >>> >>> >>> If you do "pkg_delete -r pkgA", and pkgA is a dependency of pkgB (not >>> the other way around as you have it), then pkgB will be deleted. >>> >> >> Ah, my bad. Yeah, after re-reading the wording it seems that is the >> case. >> >> What about for pkg_deinstall (part of portupgrade)? According to its >> man page, it has two options, --recursive (-r) and --upward-recursive >> (-R). >> Maybe it's just a little bit late, but what /exactly/ is the difference? >> It sounds like the --upward-recursive option would be better called >> --downward-recursive, since it will remove the ports/packages "below" >> it. > > Semantically, it is an inverted tree... i.e. the root is at the top. > > > robert. OK, I guess that makes sense. > >> So, if that is the case, would pkg_deinstall -R pkgA remove pkgB or >> not? >> > Well, I tested using pkg_deinstall -rRn, and if I were to remove the -n flag, it would be uninstalling ports all the way down to gettext. Not good. So, it would be removing 'pkgB' with this option. Any way to prevent this? -- To send me a personal email, please place [personal] in the Subject line.