From owner-freebsd-ports Mon May 1 13:34:57 2000 Delivered-To: freebsd-ports@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id E8AFF37C364 for ; Mon, 1 May 2000 13:34:03 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-07.ix.netcom.com [209.109.235.7]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id QAA11246; Mon, 1 May 2000 16:33:20 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id NAA35084; Mon, 1 May 2000 13:29:59 -0700 (PDT) To: Gary Jennejohn Cc: ports@FreeBSD.ORG Subject: Re: lists of files and directories missing from PLIST References: <200005011330.PAA04307@peedub.muc.de> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 01 May 2000 13:29:29 -0700 In-Reply-To: Gary Jennejohn's message of "Mon, 01 May 2000 15:30:42 +0200" Message-ID: Lines: 23 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * 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. * 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. Yes, that's too hairy. :) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message