Re: pkg/45136 ([MAINTAINER][PATCH] www/aws, fix DESTDIR breakage and other problems)

["OBATA Akio" <obache%netbsd.org@localhost>]

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

From: "OBATA Akio" <obache%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: pkg/45136 ([MAINTAINER][PATCH] www/aws, fix DESTDIR breakage and
 other problems)
Date: Mon, 25 Jul 2011 18:04:17 +0900

 On Sun, 24 Jul 2011 23:40:03 +0900, John Marino <netbsd%marino.st@localhost> 
wrote:
 
 >  "Why do you want to use dynamic GENERATE_PLIST?"
 >  The answer is WAY more complicated than a simple pdf option.  Believe me, I 
 > had good reason to remove the existing static list and replace it with the 
 > dynamic one.  The number of permutations of files with the entire set of 
 > options is large, and using a static list is prone to error.  Without going 
 > into a lot of detail, it would be best to accept that a dynamic PLIST is the 
 > way to go here, which will always be correct.  The existing PLIST isn't 
 > "correct" minus pdf either, it's going several existing problems with it.
 
 At least, some of files in your GENERATE_PLIST (ex. bin/aws_password, and so 
on) no need to be
 generated dynamically, so you can put those files in static PLIST.
 If some conditionally installed files are large set, you can put those files 
in  separate PLIST.* files
 and add those file names to PLIST_SRC conditionally.
 
 Disadvantage of full dynamically PLIST generation are:
 
 * We cannot track changes of installed files between version up of the package
 * We cannot confirm what files will be installed before trying to install the 
package
 * We cannot catch up accidental mis-installation, say, "some required files 
are not installed",
    or "some redundant files are installed".
 
 -- 
 OBATA Akio / obache%NetBSD.org@localhost