From owner-freebsd-ports@FreeBSD.ORG Fri Jan 14 13:55:12 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 1374616A4CE for ; Fri, 14 Jan 2005 13:55:12 +0000 (GMT) Received: from mail.bitdefender.com (ns.bitdefender.com [217.156.83.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D85AC43D49 for ; Fri, 14 Jan 2005 13:55:10 +0000 (GMT) (envelope-from apircalabu@bitdefender.com) Received: (qmail 8797 invoked from network); 14 Jan 2005 13:55:10 -0000 Received: from apircalabu.dsd.ro (10.10.15.22) by mail.dsd.ro with AES256-SHA encrypted SMTP; 14 Jan 2005 13:55:10 -0000 Date: Fri, 14 Jan 2005 15:57:45 +0200 From: Adi Pircalabu To: freebsd-ports@freebsd.org Message-ID: <20050114155745.179a1bfe@apircalabu.dsd.ro> In-Reply-To: <20050114133050.GN69532@voodoo.oberon.net> References: <20050113062739.GA28658@xor.obsecurity.org> <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> 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 13:55:12 -0000 On Fri, 14 Jan 2005 14:30:50 +0100 Kirill Ponomarew wrote: > > In my case, after port's deinstall, there will always be files left > > in${PREFIX}/portname/. Is this a reason for tagging the port > > BROKEN/IGNORE? > > Leftovers are considered to be a reason for BROKEN tag. I understand your point, it is very decent from an application to clean-up after deinstall. But sometimes it is not appropriate to complete delete all the dirs/files, especially when the files are, let's say, system-wide configuration files. What if I upgrade the software? Do I have to backup the configuration before upgrading, and then restore it after the upgrade completed? I'm too lazy for that, I'd like a smooth and easy upgrade :) In my case, it is very common for the port to change/modify/delete files at runtime, even configuration files are changed while the product is running. If this is the reason for marking the port BROKEN I'm in big trouble :| -- Adrian Pircalabu Public KeyID = 0xF902393A -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://www.bitdefender.com/