From owner-freebsd-ports@FreeBSD.ORG Fri Jan 14 14:36:44 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EE9816A4CE for ; Fri, 14 Jan 2005 14:36:44 +0000 (GMT) Received: from mail.bitdefender.com (ns.bitdefender.com [217.156.83.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2910043D58 for ; Fri, 14 Jan 2005 14:36:43 +0000 (GMT) (envelope-from apircalabu@bitdefender.com) Received: (qmail 26135 invoked from network); 14 Jan 2005 14:36:40 -0000 Received: from apircalabu.dsd.ro (10.10.15.22) by mail.dsd.ro with AES256-SHA encrypted SMTP; 14 Jan 2005 14:36:40 -0000 Date: Fri, 14 Jan 2005 16:39:17 +0200 From: Adi Pircalabu To: freebsd-ports@freebsd.org Message-ID: <20050114163917.7ecfa898@apircalabu.dsd.ro> In-Reply-To: <20050114142756.GA58907@xor.obsecurity.org> References: <20050113180504.GA26064@xor.obsecurity.org> <20050114130404.250d6e26@apircalabu.dsd.ro> <20050114112918.GF69532@voodoo.oberon.net> <1105704398.41e7b5ce7dc5e@buexe.b-5.de> <20050114144353.1aad2014@apircalabu.dsd.ro> <20050114133050.GN69532@voodoo.oberon.net> <20050114155745.179a1bfe@apircalabu.dsd.ro> <41E7D10A.8070308@FreeBSD.org> <20050114162405.2777fa0a@apircalabu.dsd.ro> <20050114142756.GA58907@xor.obsecurity.org> Organization: BitDefender X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BitDefender-SpamStamp: 1.1.2 036000040111AAAAAAE X-BitDefender-Scanner: Clean, Agent: BitDefender Qmail 1.6.1 on mail.bitdefender.com X-BitDefender-Spam: No (0) Subject: Re: HEADS UP: pkg-plist strict enforcement starting X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 14:36:44 -0000 On Fri, 14 Jan 2005 06:27:56 -0800 Kris Kennaway wrote: > The main case you need to worry about is when someone (e.g. package > cluster) does 'make install deinstall'. I see, but this does not worry me at this moment > It's OK, but not ideal, for the package to leave behind some > runtime-created files when the software has been used or configured by > the user. You should then add a pkg-deinstall message warning about > where the leftover files live, if they exist, so the administrator can > choose to delete them by hand. Well, this is what I'd been waiting for :) I noticed that many (I mean MANY) ports follow this line. Initially I thought this is the right way to do it, as a good compromise between port's needs and system's consistency after deinstall. But, after seen you initial post on this thread, I started to worry about it. If this is a correct way to handle the port, then I'll follow it :) Thank you -- Adrian Pircalabu Public KeyID = 0xF902393A -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://www.bitdefender.com/