From owner-freebsd-ports@FreeBSD.ORG Thu Apr 9 12:27:02 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 7AEBA1065672 for ; Thu, 9 Apr 2009 12:27:02 +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 2BA338FC21 for ; Thu, 9 Apr 2009 12:27:01 +0000 (UTC) (envelope-from mad@madpilot.net) Received: by megatron.madpilot.net (Postfix, from userid 1000) id 4001B130C3A; Thu, 9 Apr 2009 14:27:01 +0200 (CEST) Date: Thu, 9 Apr 2009 14:27:01 +0200 From: Guido Falsi To: Peter Pentchev Message-ID: <20090409122701.GE43377@megatron.madpilot.net> References: <20090409094545.GB43377@megatron.madpilot.net> <20090409104417.GA945@straylight.m.ringlet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090409104417.GA945@straylight.m.ringlet.net> X-Operating-System: FreeBSD 7.1-STABLE User-Agent: Mutt/1.5.19 (2009-01-05) Cc: ports@freebsd.org, Lupe Christoph Subject: Re: 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 12:27:02 -0000 On Thu, Apr 09, 2009 at 01:44:17PM +0300, Peter Pentchev wrote: > On Thu, Apr 09, 2009 at 11:45:45AM +0200, Guido Falsi wrote: > > 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. > [snip] > > I have few options at this point: > > The usual approach is to install them as .dist or .sample or something > like that, copy them with their real names, and only remove the "real" > ones if they are the same as the sample ones. This involes several > steps: [...] I see, but, my mistake, I did not explain an important detail of the prblem: the sample files are really a whole hierarchy with files being compiled to bdb files in it. Should I install the whole hierarchy with a .sample name and work as usuale with the files inside? Is this acceptable? I understood it was not. -- Guido Falsi