From owner-freebsd-ports@FreeBSD.ORG Thu Apr 9 10:03:22 2009 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB4C3106566B for ; Thu, 9 Apr 2009 10:03:22 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id A0CF58FC17 for ; Thu, 9 Apr 2009 10:03:22 +0000 (UTC) (envelope-from mad@madpilot.net) Received: by megatron.madpilot.net (Postfix, from userid 1000) id 91C15130C3A; Thu, 9 Apr 2009 11:45:45 +0200 (CEST) Date: Thu, 9 Apr 2009 11:45:45 +0200 From: Guido Falsi To: ports@freebsd.org Message-ID: <20090409094545.GB43377@megatron.madpilot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 7.1-STABLE User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Subject: squidguard and default blacklists in plist X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2009 10:03:23 -0000 Hi, I'm the maintainer of the www/squidguard port. Some time ago I have been asked to try not make the port remove the blacklists when, after installing the default ones, they were modified by the user. I fully understand and agree to this approach, so time allowing, I have made a few tests, but found some obstacles, so I'd like to ask what could be the best course of actions(hopefully not requiring a total port Makefile rewrite). I was hoping to coherce the pkg_delete program not to delete modified files based on file checksum saved in +CONTENTS, but make deinstall passes the -f flag to it(and portamster/portupgrade too I think) and it will delete files anyway, so this option is not applicable. This leaves me the situation that if I put those files in the plist they will definetly be removed. I have few options at this point: I could install them, not have them in the pkg-plist and have a deinstall script to analyze the files and delete them if and only if not modified. Could this be acceptable? Another option is simply not manage those sample files, and have a personalized make target (install-examples, f.e.) which installs them and then leave to the user their deletion, if wanted. Obviously this would have to be explained in the pkg_message. So, what is the best choice? Are there any better options? Thanks in advance for any opinions/suggestions. -- Guido Falsi