ports/158179: some packages do not fully honor -P dir option in pkg_add(1)
Chris Rees
crees at freebsd.org
Sat Jul 16 16:20:12 UTC 2011
The following reply was made to PR ports/158179; it has been noted by GNATS.
From: Chris Rees <crees at freebsd.org>
To: "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>
Cc:
Subject: Re: ports/158179: some packages do not fully honor -P dir option in pkg_add(1)
Date: Sat, 16 Jul 2011 17:13:12 +0100
--bcaec5431e90ee473804a8320a3b
Content-Type: text/plain; charset=ISO-8859-1
On 16 Jul 2011 17:04, "Stephen Montgomery-Smith" <stephen at missouri.edu>
wrote:
>
> 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:
>> > For example, suppose the C source code contains something like:
>> > char applications_dir = "/usr/local/share/applications";
>> > and this is filled in by the ./configure script.
>> >
>> > 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 software
itself.
Sorry, poor wording on my part.
If it was compiled as prefix=/usr/local, that's how it'll be installed,
regardless of your -p argument.
Chris
--bcaec5431e90ee473804a8320a3b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<p><br>
On 16 Jul 2011 17:04, "Stephen Montgomery-Smith" <<a href=3D"m=
ailto:stephen at missouri.edu">stephen at missouri.edu</a>> wrote:<br>
><br>
> On 07/16/2011 10:53 AM, Chris Rees wrote:<br>
>><br>
>><br>
>> On 16 Jul 2011 16:38, "Stephen Montgomery-Smith" <<a =
href=3D"mailto:stephen at missouri.edu">stephen at missouri.edu</a><br>
>> <mailto:<a href=3D"mailto:stephen at missouri.edu">stephen at missour=
i.edu</a>>> wrote:<br>
>> =A0> For example, suppose the C source code contains something =
like:<br>
>> =A0> char applications_dir =3D "/usr/local/share/applicati=
ons";<br>
>> =A0> and this is filled in by the ./configure script.<br>
>> =A0><br>
>> =A0> How is that handled?<br>
>> =A0><br>
>><br>
>> It's not.<br>
>><br>
>> Remember what a package is, literally the files from the plist tar=
red<br>
>> with some magic +FILEs and the pkg-*install files- if paths are<br=
>
>> hardcoded in objects that's how it'll be installed.<br>
><br>
><br>
> What if some of the installation programs are binaries, and "/usr=
/local" is hard coded into installation binaries or scripts provided b=
y the software itself.</p>
<p>Sorry, poor wording on my part.</p>
<p>If it was compiled as prefix=3D/usr/local, that's how it'll be i=
nstalled, regardless of your -p argument.</p>
<p>Chris</p>
--bcaec5431e90ee473804a8320a3b--
More information about the freebsd-ports-bugs
mailing list