Date: Tue, 11 Nov 2003 13:37:46 -0700 (MST) From: Warner Losh <imp@FreeBSD.org> To: jhein@timing.com, imp@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/56621: bad link in octave when install package using pkg_add -p Message-ID: <200311112037.hABKbkuV042635@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
Synopsis: bad link in octave when install package using pkg_add -p
State-Changed-From-To: closed->open
State-Changed-By: imp
State-Changed-When: Tue Nov 11 13:37:32 MST 2003
State-Changed-Why:
The audit trail says 'If you want to install a package to a
non-standard location, it must be build with the same prefix' is true,
but not completely relevant here.
The problem is that we're doing a pkg_add -p. It is documented to
work, including a number of things that are done to facilitate its
working.
What we want to do is to install the package into
/this/is/a/path/to/my/flash/usr/local after building with a prefix of
/usr/local. The package will be run with the long path above really
being /usr/local (eg, the tree from /this/is/a/path/to/my/flash on
down will be put onto the flash's at /).
If this were the base system, we'd want
make install DESTDIR=/this/is/a/path/to/my/flash
but that doesn't seem to be supported by the ports system at this time
(although there are a number of places in bsd.port.mk that kinda use
DESTDIR, it doesn't work and past patches to fix it have been
rejected).
Or put another way: What's the right thing to do in our situation? We
want to install the package in one place, but we know that it will be
running in a different place with the PREFIX we built it with.
Warner
P.S. This patch appears to cause no harm.
http://www.freebsd.org/cgi/query-pr.cgi?pr=56621
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311112037.hABKbkuV042635>