On 2010.9.1 6:41 AM, eric.b...@barclayscapital.com wrote:
> Hey, guys, first, thanks for your good work on this o-so-important module.
>
> I recently set up Perl for our group for 3 platforms (Linux 32-/64-bit and
> Solaris)
> and decided to use a single lib dir and break out the scripts and
executables into
> platform-specific directories keyed on the output of `uname -p`. So, I have:
>
> ~/our_perl/lib # modules
> ~/our_perl/i686 # 32-bit exe's
> ~/our_perl/i86_64 # 64-bit exe's
> ~/our_perl/sparc # Solaris exe's
> ~/our_perl/man # Man pages
>
> The problem I ran into was in my choice to use INSTALL_BASE. Generally
> speaking,
> it works fine, but looking a bit deeper into the code, it appears that there
are no
> overrides for specific sections like INSTALLBIN, INSTALLSCRIPT,
INSTALLMAN1DIR, etc.,
> so I reverted to using PREFIX, but I'd like to suggest that, if that's
actually true,
> you mention that in the docs for INSTALL_BASE. Some weird stuff happened
when I added
> INSTALLBIN to the Makefile.PL command line.
Could you be more specific what that "weird stuff" was? And what you mean by
there being no overrides? You should be able to set INSTALL_BASE and supply
INSTALLBIN, etc... individually like so:
perl Makefile.PL INSTALL_BASE=~/our_perl INSTALLBIN=~/our_perl/sparc/bin
--
170. Not allowed to "defect" to OPFOR during training missions.
-- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
http://skippyslist.com/list/
