On Tuesday 13 January 2004 23:13, Christian Goetze wrote:
> Pretty sure this must be an FAQ, but it is amazingly hard to find anything
> really descriptive.
>
> A useful tidbit was
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg00779.html
>
> which is why I am sending this to this list. My problem is a little bit
> more complex.
>
> I need to do a custom perl build (mainly to support 64bit int), and make a
> binary, _relocatable_ RPM out of it, including a variety of CPAN modules,
> some of which are XS modules. In addition, that perl needs to provide
> libperl.so for embedding into our application.
Do you really want _one_ rpm ? Why not use multiple dependant rpms instead ?
> Currently, I am doing a horrid process which includes installing my perl,
> then adding the CPAN modules, then packaging the RPM out of the installed
> location.
You are not supposed to build from installed location, but from the buildroot
one package at a time.
> I wished I could build and temporarily install perl into my buildroot,
> then add the CPAN modules into that perl, then package it and install the
> rpm and have everything work as it should.
First, build one perl package for your custom perl, and name it as you want.
Then build other package, having your custom perl package as build
dependency.
> I understand how I can build CPAN modules within my buildroot and package
> them, but that relies on perl being already installed. What I need is some
> way to make this work without perl being installed in its final production
> location, but at best installed into some temporary buildroot.
Have you tried building inside a chroot ?
> Any tips would be wildly appreciated. At this point, I think my only
> recourse is to grep the binaries for my buildroot path and substitute that
> with the final production path, possibly in a %post hook if I need
> relocatability at installation time....
relocability isn't so nice, as it breaks dependency.
--
A traffic light will always turn yellow as you approach it
-- Murphy's Driving Laws n�15
