From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31842 invoked by uid 1002); 21 May 2003 20:02:35 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 25388 invoked from network); 21 May 2003 20:02:20 -0000 From: Martin Schlemmer Reply-To: azarah@gentoo.org To: John Cc: Gentoo-Dev In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-yFoXWOd31iXj1nMlAs0M" Organization: Message-Id: <1053547436.10390.51.camel@nosferatu.lan> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4- Date: 21 May 2003 22:03:56 +0200 Subject: Re: [gentoo-dev] ebuild: Hard coded paths X-Archives-Salt: 73e550d7-8863-48c3-800b-f9a6c9493063 X-Archives-Hash: 773083baaa2559008e9d44ec43a11724 --=-yFoXWOd31iXj1nMlAs0M Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2003-05-21 at 21:54, John wrote: > Hello, >=20 > I am attempting to create an ebuild for ircd-hybrid. This irc server > requires that the path to where it is installed get compiled into the > binary. I have verified that $P does not cut it (it is the location > of the temorary image directory). >=20 > How is something like this handled in portage? Can I know during the=20 > build where the final destination will be? Should I just "hard code" wha= t=20 > is probably the typical case? So cant you just tell it at configure time it will be in /foo/bar, but still install it to "$D/foo/bar" ? Or install it by hand (dobin foo; dolib bar; etc)? Alternative if not, you can do what we do in divx4linux: dosed -e 's|c:\\trace_b.txt|/dev/null\x00\x00\x00\x00\x00|' \ /usr/lib/libdivxencore.so Regards, --=20 Martin Schlemmer Gentoo Linux Developer, Desktop/System Team Developer Cape Town, South Africa --=-yFoXWOd31iXj1nMlAs0M Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA+y9usqburzKaJYLYRAkEnAJ9mWeD9Pu9EBgmv/yFPUGv9h6DIFQCeNeI5 6IOj5akYWuq1aR9HDCGfo5o= =poGw -----END PGP SIGNATURE----- --=-yFoXWOd31iXj1nMlAs0M--