ports/69266: www/squid delete existing files when "make deinstall"

Thomas-Martin Seck tmseck-lists at netcologne.de
Mon Jul 19 17:50:28 UTC 2004


The following reply was made to PR ports/69266; it has been noted by GNATS.

From: tmseck-lists at netcologne.de (Thomas-Martin Seck)
To: bug-followup at freebsd.org
Cc: Tsurutani Naoki <turutani at scphys.kyoto-u.ac.jp>
Subject: Re: ports/69266: www/squid delete existing files when "make deinstall"
Date: 19 Jul 2004 17:47:39 -0000

 * Tsurutani Naoki <turutani at scphys.kyoto-u.ac.jp>:
 
 >>Description:
 >        www/squid removes many files in $PREFIX/etc/squid when it is deinstalled.
 >        This port has no pkg-plist, and generate it in Makefile.
 >        It seems to me that the generating way is simple listing of
 >        existing files just after installation.
 >        But this procedure includes foreign files from www/squid.
 >        MD5 checksums are also recorded, so changed files are not removed,
 >        but many files that are not changed, cf. configuration files, are
 >        removed.
 
 Oops. I admit I did not think about this case when I switched to dynamic
 plist creation since I used to use a copy of the original directories
 for modifications.
 
 >>How-To-Repeat:
 >        always.
 
 Fortunately, you can avoid this.
 
 If you want to customize your icons and/or the error pages, just put
 these modified directories where the PLIST creation script
 does not look for them.  Then use the 'icon_directory' and
 'error_directory' configuration options to tell squid where your custom
 files live. This will preserve them.
 
 >        
 >>Fix:
 >        I don't know, but I think the way of generating PLIST should be improved.
 
 I see the problem, but the only sure-fire way to avoid this would be to
 stage a fake installation first, create the package list and then copy
 this installation into the PREFIX dir, like firefox does. I am not
 really fond of this and I would like to avoid it. Mind you that other
 ports suffer from the same problem, e.g. vim. And while this will
 preserve locally added files, it will still end in modified files being
 overwritten on every update.



More information about the freebsd-ports-bugs mailing list