Christian Goetze <[EMAIL PROTECTED]> writes: >> On Tue, 13 Jan 2004, Christian Goetze wrote: >> >>>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, >> >> You need to do exactly that? It would normally make more sense to build >> a package for perl, then separate RPMs for each CPAN module >> using a tool like cpan2rpm, makerpm.pl or cpanflute. > >The problem with that process is that you need to install perl prior to >packaging the modules. That install step usually requires root (or a world >writeable /usr - pick your poison). Since we have a non-standard perl >build and need libperl.so for embedding into our app, this is not an >option.
Hence the ActiveState-oid scheme to install to /tmp/longsillynamewecanpatchlater > >The whole problem would be a lot simpler if perl used FindBin on itself, >i.e. would not hardwire its load paths but instead use the location of the >perl binary (or the location of the binary of the application embedding >perl). A. It doesn't B. It would be slower C. There are "race" cases which open security holes On platfroms where $^X is reliable we _could_ use that.
