From owner-freebsd-current Mon May 8 13:23:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 593B737BBFF; Mon, 8 May 2000 13:23:31 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA00931; Mon, 8 May 2000 13:23:31 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 8 May 2000 13:23:30 -0700 (PDT) From: Kris Kennaway To: Satoshi - Ports Wraith - Asami Cc: Kenneth Wayne Culver , freebsd-current@freebsd.org Subject: Re: proposed pkg_delete change In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 May 2000, Satoshi - Ports Wraith - Asami wrote: > Be careful about that "aren't currently used by anything else" part. > If you already had a port A installed, and then later installed B > (which just happens to depend on A), you could get A erased when you > erase B. Have a -n mode (-nothing) which prints a list of actions it would take so you can review. > You probably need to change pkg_add too, so that it will note > somewhere on A's dependency list that it was installed by which port, > and let pkg_delete check it. This could be done with an extra binary field in +REQUIRED_BY showing whether the package was installed by a parent. pkg_delete would recursively remove it if 1) There was only a single +REQUIRED_BY entry, and 2) The parent package bit is set. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message