Rick Chisholm wrote:
> Guido Falsi wrote:
>> On Tue, Jan 20, 2009 at 10:09:25PM -0800, Doug Barton wrote:
>>
>>> Guido Falsi wrote:
>>> > Since ports are expected not to leave files behind when deinstalled,
>>>
port logic checks on first install if ${DATADIR} exists. If it does it
On Wed, Jan 21, 2009 at 10:26:19AM -0500, Rick Chisholm wrote:
>> I agree. I was thinking if it could be acceptable to add an option to
>> the port for installing/not installing the sample blacklists and not
>> adding those to the plist anyway. This could be easier to handle.
>> Perhaps also more l
Guido Falsi wrote:
On Tue, Jan 20, 2009 at 10:09:25PM -0800, Doug Barton wrote:
Guido Falsi wrote:
> Since ports are expected not to leave files behind when deinstalled,
port logic checks on first install if ${DATADIR} exists. If it does it
will NOT be created/populated and NOT include
On Tue, Jan 20, 2009 at 10:09:25PM -0800, Doug Barton wrote:
> Guido Falsi wrote:
> > Since ports are expected not to leave files behind when deinstalled,
> > port logic checks on first install if ${DATADIR} exists. If it does it
> > will NOT be created/populated and NOT included in the plist, and
Guido Falsi wrote:
> Since ports are expected not to leave files behind when deinstalled,
> port logic checks on first install if ${DATADIR} exists. If it does it
> will NOT be created/populated and NOT included in the plist, and not
> removed on deinstall.
>
> On the contrary if it does not find
Rick Chisholm wrote:
Hello:
I recently did a SG 1.3 to 1.4 portupgrade and it seems to have cleared
out my /var/db/squidGuard dir. Does that make sense?
Hi!
It does make sense. It depends on how the port was first installed.
When taking maintainership I did not modify the original logic.
