Date: Thu, 9 Apr 2009 14:27:01 +0200 From: Guido Falsi <mad@madpilot.net> To: Peter Pentchev <roam@ringlet.net> Cc: ports@freebsd.org, Lupe Christoph <lupe@lupe-christoph.de> Subject: Re: squidguard and default blacklists in plist Message-ID: <20090409122701.GE43377@megatron.madpilot.net> In-Reply-To: <20090409104417.GA945@straylight.m.ringlet.net> References: <20090409094545.GB43377@megatron.madpilot.net> <20090409104417.GA945@straylight.m.ringlet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090409122701.GE43377>