[gentoo-dev] ebuild: Hard coded paths

[gentoo-dev] ebuild: Hard coded paths

[John]

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?

Thanks,

John

--
gentoo-dev@gentoo.org mailing list

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

[Martin Schlemmer]

[-- 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 --]

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

[Kumba]

	I always thought integrating an IRCd would be a pain in the neck into 
portage because of their method of requiring the user to edit header 
files before compiliation, and with instances like you've mentioned.

	If hybrid is any example, adding others, like Bahamut, Unreal, Tiamat, 
etc.., will probably be...."fun".

--Kumba


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?
> 
> Thanks,
> 
> John
> 
> --
> gentoo-dev@gentoo.org mailing list
> 
> 



--
gentoo-dev@gentoo.org mailing list

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

[John]

On Wed, 21 May 2003, Martin Schlemmer wrote:

> So cant you just tell it at configure time it will be in /foo/bar, but
> still install it to "$D/foo/bar" ?

It does not honor any configure options for locations of stuff.  One needs 
to manually change config.h.

> Or install it by hand (dobin foo; dolib bar; etc)?

Yeah...I may need to put the "final" locations in config.h and then 
install by hand.  That is apparently how the BSD port gets it to work.

> 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


I sort of wish the same thought hadn't occured to me :)

John

--
gentoo-dev@gentoo.org mailing list

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

[Erik S. Johansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 21 May 2003 23:05, Kumba wrote:
> I always thought integrating an IRCd would be a pain in the neck into
> portage because of their method of requiring the user to edit header
> files before compiliation, and with instances like you've mentioned.
>
> 	If hybrid is any example, adding others, like Bahamut, Unreal, Tiamat,
> etc.., will probably be...."fun".

I used to do a little work on the IRCD-Hybrid team... If you're looking at 
hybrid 7, it should be ok enough, but hybrid 6 (which is still widely used, 
a.o. on the EFNet server i'm on) will require quite extensive patches to 
config.h as almost all settings are defined in there, and the defaults wont 
do much good if you plan on actually having users on it.

Is there anything but the kernel sources that gets installed as a source 
package which you then must manually configure and compile? hybrid 6 would 
fit very well into that category if so.


- --Erik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+y9+ids9m9uhAobARAvBmAJ95UfgJjkTScDeWyzkR9l+tnln6DACgkFKW
9WBvLxrkVOaHxPtmE0ZDE2o=
=q0ev
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list

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

[John]

On Wed, 21 May 2003, Erik S. Johansen wrote:

> I used to do a little work on the IRCD-Hybrid team... If you're looking at 
> hybrid 7, it should be ok enough, but hybrid 6 (which is still widely used, 
> a.o. on the EFNet server i'm on) will require quite extensive patches to 
> config.h as almost all settings are defined in there, and the defaults wont 
> do much good if you plan on actually having users on it.

I was working with Hybrid 6...

For my application, Hybrid 7 may be the way to go (small private network).  
It has a configure script that does the right thing. Thanks for the idea.

John

--
gentoo-dev@gentoo.org mailing list