From owner-freebsd-ports@FreeBSD.ORG Sun Jul 17 11:23:52 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F40B1065672 for ; Sun, 17 Jul 2011 11:23:52 +0000 (UTC) (envelope-from marco.broeder@gmx.eu) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by mx1.freebsd.org (Postfix) with SMTP id F23318FC08 for ; Sun, 17 Jul 2011 11:23:51 +0000 (UTC) Received: (qmail invoked by alias); 17 Jul 2011 10:57:11 -0000 Received: from port-92-195-20-164.dynamic.qsc.de (EHLO localhost) [92.195.20.164] by mail.gmx.net (mp011) with SMTP; 17 Jul 2011 12:57:11 +0200 X-Authenticated: #23197544 X-Provags-ID: V01U2FsdGVkX18GPoh70hAGrgFgxjx57ypW0tDMRb+Jxb1M81/Myq QWx3oRsbPXV77j From: Marco =?iso-8859-1?q?Br=F6der?= To: freebsd-ports@freebsd.org Date: Sun, 17 Jul 2011 12:55:10 +0200 User-Agent: KMail (FreeBSD) References: <4E20FADE.6060103@missouri.edu> <4E21B9C1.9020102@missouri.edu> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3525883.hoGy8Ay3LY"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201107171256.19370.marco.broeder@gmx.eu> X-Y-GMX-Trusted: 0 Subject: Re: ports/158179: some packages do not fully honor -P dir option in pkg_add(1) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: marco.broeder@gmx.eu List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2011 11:23:52 -0000 --nextPart3525883.hoGy8Ay3LY Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Sat July 16 2011 18:21:12 Chris Rees wrote: > Bear in mind they should work fine if the port doesn't hardcode absolute > paths. Yes, they actually do! Please do not remove them, because they are not as=20 buggy as it is claimed here. I often use the -p option for testing of my=20 tinderbox -exp packages and it works fine. A package is basically the same as an installed port - just with some=20 additional pkg meta data files all packed into a compressed tarball. If a=20 package contains hardcoded paths then the port is buggy not the package or= =20 pkg_add. It is a general rule that ports should respect ${PREFIX}. If they = do=20 not those ports need to be fixed. I find it weird to think the -p / -P options should be removed from pkg_add= =2E=20 Do not castrate the tool if some ports are buggy! Thanks! =2D-=20 Regards --nextPart3525883.hoGy8Ay3LY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- iQIcBAABCAAGBQJOIr/TAAoJEEjQ6Txo1AoUfdkQAKJ52+osAQdFWudPaPJ/Th7C UBRSlJuKmjDCRWzChPVaG7OkoFtkg/sasQ9iwYhvMvYUlOjBjzUuGaAH+zwW9aoW 3QJBc9rFSr6InW1PcczsM5tsVoebP3mjSmW8sdwyGpgI+OdWFe5Zq4kJme1NtwoP JkiI2tnTtAZIWYZ7KENWsppFozu1kc08uzj+9+Y2WdfRWbeyFFp5OcK8DrkygDag TIOAHQACmRgsV0if+Qu0QZmxrRe22Zui5ovB6pqX9uXC9pOHBSQCv/orqrsBJKB2 RYHTDgCDLZLW947VxhxWjt7r30uHwrOQuyWCjrzCZF31pBf7dEbKAGeE3XzpGqMa tXVb/vCnzBwYXzSZ+KqlU+hbw2x7NALrNEOtHyrhCnposVZ0JwZ12C5OtvsFCx6m vQ1sFKz4xkrdsMypJqQxOyvCHwjtMtDW/X+lFbz7wTUxLwf4QhhwOYChljYtMJCe X//9bgNYlZ1TYuWxaeBJXiYTGQiHH1yLyPb25eckCa7KhU29ZOBp8pPGDjTpuPqK ZGoBcYnTnckakIOA4WQGGUz4INVihxSiPRw39fQR10zRYldEQCLysgczr0scXG6w Zt4TWkT8QVnPJr2D309CbE1WwCtRPJyiMll8O/roq2JbjfQ/yX+039Jbez/pvDSb U3ZtChxflvcwX0FCqcvW =pCVH -----END PGP SIGNATURE----- --nextPart3525883.hoGy8Ay3LY--