From owner-freebsd-ports  Thu Jul 31 00:20:02 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA11841
          for ports-outgoing; Thu, 31 Jul 1997 00:20:02 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA11803
          for <freebsd-ports@FreeBSD.ORG>; Thu, 31 Jul 1997 00:19:58 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id AAA20205; Thu, 31 Jul 1997 00:19:16 -0700 (PDT)
To: scott@statsci.com
cc: freebsd-ports@FreeBSD.ORG
Subject: Re: how to handle compiled in paths? 
In-reply-to: Your message of "Wed, 30 Jul 1997 20:27:53 PDT."
             <199707310327.UAA01673@one.sabami.seaslug.org> 
Date: Thu, 31 Jul 1997 00:19:14 -0700
Message-ID: <20201.870333554@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I was just noticing something with my nmh port...it seems that the prefix is 
> compiled into the binaries, so if you make a package out of it, you can't
> retarget the prefix with the pkg_add -p option (without recompilation, which
> kind of defeats the purpose of the package & its -p option).  How is this
> kind of stuff normally handled?

You repeat the @cwd line twice at the top of the package's PLIST,
"stapling" it to the canned prefix and preventing a -p override.  Not
every user's desire, of course, this still at least ensures that
what's installed will work and is probably the best that can be done
under the circumstances.

						Jordan