From owner-freebsd-ports  Wed Aug 28 19:42:37 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA04698
          for ports-outgoing; Wed, 28 Aug 1996 19:42:37 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca11-01.ix.netcom.com [199.35.209.161])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA04682
          for <freebsd-ports@freebsd.org>; Wed, 28 Aug 1996 19:42:33 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id TAA21898; Wed, 28 Aug 1996 19:42:25 -0700 (PDT)
Date: Wed, 28 Aug 1996 19:42:25 -0700 (PDT)
Message-Id: <199608290242.TAA21898@silvia.HIP.Berkeley.EDU>
To: james@ican.net
CC: jkh@time.cdrom.com, freebsd-ports@freebsd.org
In-reply-to: <Pine.BSI.3.95.960828221232.27041D-100000@expresslane.ca> (message from James FitzGibbon on Wed, 28 Aug 1996 22:15:23 -0400 (EDT))
Subject: Re: Should this port go in ?
From: asami@freebsd.org (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * What about the issue of compressed vs. uncompressed manpages ?  To solve
 * this, I could just make two PLISTS in ${FILESDIR}, and based on the
 * variable NOMANCOMPRESS copy one or the other into ${PKGDIR} before the
 * install was registered.  Acceptable ?

Please don't do this, if it's only manpages.  I do "grep foo
/usr/ports/*/*/pkg/PLIST" all the time to find the port that installed
a certain file.

This manpage issue has been bothering me for a while.  Maybe we can
add a flag to pkg_create to handle this or something.

 * I agree with both of you on the complexity of the Makefile.  It's damn
 * ugly looking at it a couple of hours later.  Ah, how the youthful glow
 * does dim.  I'll save it for ports that need it.

If the list of files that change is really quite large, then that's
ok.  (There are already some ports that do this, most notably the
pkfonts ports, they have separate PLISTs for each resolution.)

Satoshi