Re: [gentoo-dev] ebuild: Hard coded paths

[Martin Schlemmer <azarah@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On Wed, 2003-05-21 at 21:54, John wrote:
> Hello,
> 
> 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).
> 
> How is something like this handled in portage?  Can I know during the 
> build where the final destination will be?  Should I just "hard code" what 
> 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,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]