From owner-freebsd-ports  Sun Aug  4 21:42:54 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA18272
          for ports-outgoing; Sun, 4 Aug 1996 21:42:54 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA18266
          for <ports@freebsd.org>; Sun, 4 Aug 1996 21:42:52 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id VAA07467; Sun, 4 Aug 1996 21:41:44 -0700 (PDT)
To: James FitzGibbon <james@nexis.net>
cc: ports@freebsd.org
Subject: Re: Opinions of port vs package please 
In-reply-to: Your message of "Mon, 05 Aug 1996 00:21:14 EDT."
             <Pine.BSI.3.94.960805001557.12034A-100000@bdd.net> 
Date: Sun, 04 Aug 1996 21:41:44 -0700
Message-ID: <7465.839220104@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Let's say the port allows you to choose which binaries it will build.
> When making the package, I plan to build all the binaries rather than
> second guess the people using it.  So, I put all the installed binaries
> into the PLIST.  Now, if the program is installed as a port rather than a
> package, the list of installed files might be incorrect, depending on
> which binaries that person chose to install.  

There's one easy solution, though you probably won't like it. :-)

Override the fake-pkg target in your ports Makefile and have it
synthesize a PLIST rather than using the pkg/PLIST file.  You could
even make it an easier task to use just _part_ of the pkg/PLIST file
(for all the invariant pieces) by surrounding those parts with
`@comment <sometoken>' lines.  Then you just append entries for each
binary you've selected to install and whap the results into
${PKG_DBDIR}/${PKGNAME}/PLIST directly.  Voila.  Problem solved.

					Jordan