ports/158179: some packages do not fully honor -P dir option in pkg_add(1)
adrian at freebsd.org
Sun Jul 17 02:40:10 UTC 2011
The following reply was made to PR ports/158179; it has been noted by GNATS.
From: Adrian Chadd <adrian at freebsd.org>
To: Chris Rees <crees at freebsd.org>
Cc: "bug-followup at freebsd.org" <bug-followup at freebsd.org>, "current at freebsd.org" <current at freebsd.org>,
"freebsd at sopwith.solgatos.com" <freebsd at sopwith.solgatos.com>, Stefan Bethke <stb at lassitu.de>,
Stephen Montgomery-Smith <stephen at freebsd.org>
Subject: Re: ports/158179: some packages do not fully honor -P dir option in pkg_add(1)
Date: Sun, 17 Jul 2011 10:02:38 +0800
Unless say, you're doing package installation outside of a
chroot/jail, to populate something inside a chroot/jail before you
start said chroot/jail.
On 17 July 2011 00:13, Chris Rees <crees at freebsd.org> wrote:
> On 16 Jul 2011 17:04, "Stephen Montgomery-Smith" <stephen at missouri.edu>
>> On 07/16/2011 10:53 AM, Chris Rees wrote:
>>> On 16 Jul 2011 16:38, "Stephen Montgomery-Smith" <stephen at missouri.edu
>>> <mailto:stephen at missouri.edu>> wrote:
>>> =A0> For example, suppose the C source code contains something like:
>>> =A0> char applications_dir =3D "/usr/local/share/applications";
>>> =A0> and this is filled in by the ./configure script.
>>> =A0> How is that handled?
>>> It's not.
>>> Remember what a package is, literally the files from the plist tarred
>>> with some magic +FILEs and the pkg-*install files- if paths are
>>> hardcoded in objects that's how it'll be installed.
>> What if some of the installation programs are binaries, and "/usr/local"
> is hard coded into installation binaries or scripts provided by the softw=
> Sorry, poor wording on my part.
> If it was compiled as prefix=3D/usr/local, that's how it'll be installed,
> regardless of your -p argument.
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org=
More information about the freebsd-ports-bugs