From owner-freebsd-ports  Thu Jul 31 02:59:11 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA24314
          for ports-outgoing; Thu, 31 Jul 1997 02:59:11 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA24307
          for <freebsd-ports@FreeBSD.ORG>; Thu, 31 Jul 1997 02:59:08 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id CAA10512; Thu, 31 Jul 1997 02:59:00 -0700 (PDT)
Date: Thu, 31 Jul 1997 02:59:00 -0700 (PDT)
Message-Id: <199707310959.CAA10512@silvia.HIP.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: scott@statsci.com, freebsd-ports@FreeBSD.ORG
In-reply-to: <20201.870333554@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: how to handle compiled in paths?
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * 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.

Um, this is not the case of "doctor, it hurts when I shoot my feet!",
Jordan. ;)

What he is asking is how to make ports not compile in the compile-time
PREFIX into the binaries so the users can "pkg_add -p /wherever" to
install the package anywhere s/he wants.  (Besides, your method will
defeat ports which can change the PREFIX at compile time.)

The short answer is that we don't have any provisions of that
currently; the long answer to that is that it may be doable (I do have
some ideas), but it is very hard.

Satoshi