From owner-freebsd-ports Tue May 2 13:59: 3 2000 Delivered-To: freebsd-ports@freebsd.org Received: from peedub.muc.de (p3E9B8F57.dip.t-dialin.net [62.155.143.87]) by hub.freebsd.org (Postfix) with ESMTP id BA45837BDBC; Tue, 2 May 2000 13:58:55 -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 WAA08799; Tue, 2 May 2000 22:09:27 +0200 (CEST) Message-Id: <200005022009.WAA08799@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: asami@freebsd.org (Satoshi - Ports Wraith - 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 "01 May 2000 13:29:29 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 May 2000 22:09:27 +0200 From: Gary Jennejohn Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satoshi - Ports Wraith - Asami writes: > * From: Gary Jennejohn > > * 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. > >According to the handbook, you can do something like > >@unexec rmdir %D/lib/vile 2>/dev/null || true > >to remove the directory only if it is empty, and fail quietly if it >doesn't so the user doesn't get scared. > Yes, but you say that leaving a file/directory behind will become a fatal error at some time in the future. If I leave some files in a dir because I know another port needs them, then that should not be considered fatal. How to differentiate, that's the problem. I guess the simplest solution is just to redundantly install the files in unique directories :( --- 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