Re: pkg/48967: Package submission to add HTML documentation for Python 3.4

[David H.Gutteridge <dhgutteridge%sympatico.ca@localhost>]

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

From: David H.Gutteridge <dhgutteridge%sympatico.ca@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: pkg/48967: Package submission to add HTML documentation for Python 
3.4
Date: Sun, 13 Jul 2014 23:42:52 -0400

 On 2014-07-06, at 8:32 PM, David H. Gutteridge wrote:
 >> From: Aleksej Saushev <asau%inbox.ru@localhost>
 >> To: pkgsrc-bugs%NetBSD.org@localhost
 >> Subject: Re: pkg/48967: Package submission to add HTML documentation =
 for Python
 >>     3.4
 >> Date: Sun, 06 Jul 2014 22:50:05 +0400
 >>=20
 >> dhgutteridge%sympatico.ca@localhost writes:
 >>=20
 >>> do-install:
 >>>       cd ${WRKSRC} && pax -rw -pe [a-z]* =
 ${DESTDIR}${PREFIX}/${HTMLDIR}
 >>=20
 >> Please, don't use "-pe", this breaks unprivileged builds on FreeBSD, =
 use "-pp" instead.
 >>=20
 >>>       cd ${DESTDIR}${PREFIX} && ${FIND} ${HTMLDIR} -type f -print =
 >>${PLIST_SRC}
 >>=20
 >> What is the reason not to use static PLIST?
 >=20
 > Hello,
 >=20
 > I couldn't tell you why there isn't a static PLIST, I followed what's
 > been established in py26-html-docs and py27-html-docs. (The -pe vs.
 > -pp issue is present in those packages' current make files too.)
 
 Re. dynamic PLIST use, all I can see is that related packages have
 followed this method from the beginning, back to py21-html-docs in
 2002. I'd guess it's in part because "make print-PLIST" won't work,
 so the means to generate a PLIST was put in the make file rather
 than a PLIST being pre-generated and committed, perhaps for easy
 (self-)documentation of how the PLIST is generated.
 
 Dave