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

From: Roland Illig <roland.illig@gmx.de>
To: "Simon J. Gerraty" <sjg@crufty.net>
Cc: gnats-bugs@netbsd.org
Subject: Re: pkg/26603
Date: Sun, 13 Feb 2005 05:29:08 +0100

 Simon J. Gerraty wrote:
 > Hi,
 > 
 > sorry about the long wait..  can you be more explicit about the files
 > that are being overwritten?  
 > 
 > The problem from my end is that attempting to generate a PLIST for
 > this package via the makefile is tricky to say the least.  
 > The existing logic in the makefile to build PLIST_SRC is not really
 > correct - and nor is your patch I'm afraid.  They may well work for
 > one system - but one only.  Thus making a binary pkg with this
 > approach wouldn't be a good idea.
 > 
 > It would probably be helpful to identify the exact problem you see, so
 > that install-mk can be fixed to address it, and then it would probably
 > make sense for install-mk to generate a PLIST (or rather +CONTENTS
 > file) to reflect what it is doing, rather than have the makefile try
 > to emulate it.
 
 Hello Simon,
 
 I think the best way to solve the problem would be to integrate the 
 PLIST generation into the install-mk script. It could do this for every 
 file:
 
 - Check if the target file does exist and then ...
    * cancel installation?
    * just ignore the file?
 - Write the file name to the PLIST
 
 The install-mk script could be called like this:
 
 do-install:
 	${WRKSRC}/install-mk PREFIX=${PREFIX} DESTDIR="/share/mk" \
 	PLIST=${WRKDIR}/.PLIST_SRC
 
 The exact way depends on how the PLISTs are handled during installation. 
 I have no idea about them, but I could try to find out.
 
 Roland