From owner-freebsd-ports Wed Jul 30 23:48:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA10052 for ports-outgoing; Wed, 30 Jul 1997 23:48:20 -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 XAA10042 for ; Wed, 30 Jul 1997 23:48:15 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id XAA14704; Wed, 30 Jul 1997 23:47:30 -0700 (PDT) Date: Wed, 30 Jul 1997 23:47:30 -0700 (PDT) Message-Id: <199707310647.XAA14704@silvia.HIP.Berkeley.EDU> To: scott@statsci.com CC: freebsd-ports@FreeBSD.ORG In-reply-to: <199707310327.UAA01673@one.sabami.seaslug.org> (message from Scott Blachowicz on Wed, 30 Jul 1997 20:27:53 -0700) 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 * 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? It is not. :) Satoshi