From owner-freebsd-ports Mon May 1 6:35:25 2000 Delivered-To: freebsd-ports@freebsd.org Received: from peedub.muc.de (p3E9B8F2E.dip.t-dialin.net [62.155.143.46]) by hub.freebsd.org (Postfix) with ESMTP id 79D3737B911 for ; Mon, 1 May 2000 06:35:20 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id PAA04307; Mon, 1 May 2000 15:30:42 +0200 (CEST) Message-Id: <200005011330.PAA04307@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: asami@cs.berkeley.edu (Satoshi Asami) Cc: ports@FreeBSD.ORG Subject: Re: lists of files and directories missing from PLIST Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 30 Apr 2000 18:54:46 PDT." <200005010154.SAA08504@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 May 2000 15:30:42 +0200 From: Gary Jennejohn Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satoshi Asami writes: >At some point in the future, I would like to make failure of this test >fatal, i.e., the package build will fail if a port installs a file it >doesn't say it does, or leaves an extra directory behind. There are >cases where files *are* supposed to be left behind (like info/dir), so >we probably need an extra directive to speficy that. > I'm wondering about ports like vile and xvile (which I maintain) which share directories (specifically lib/vile and doc/vile). If a user has both installed and decides to delete on of them we don't want to pull the rug out from under his feet by arbitrarily nuking everything. We could force the install of files common to 2 or more ports into unique directories, but then the user ends up with redundancies. The other possibility would be to check dependencies and see whether the files to be deleted are required by another installed port, but that can get hairy. Any ideas ? --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message