[Shipwright] Building perl in vessels with 'perl' in their names

sunnavy sunnavy at bestpractical.com
Fri Jun 15 18:15:17 EDT 2012

Good catch, I'll update code to reflect this.
Thank you!


On 12-06-15 15:06, David Good wrote:
> I've found an interesting bug(?) with Shipwright.  If you build a vessel
> containing a perl installation using an --install-base directory
> containing the string 'perl', Configure will, by default, install all of
> its core modules under './lib' rather than './lib/perl5'. 
> I guess the authors of Configure decided that if your prefix already
> includes 'perl' it would be redundant to put things under a 'perl5'
> subdirectory.  Unfortunately, the Shipwright wrapper scripts and shell
> source files assume that everything is under './lib/perl5'.  Since my
> RPM package is going to have a name that includes 'perl', I'm pretty
> much guaranteed that Configure will see it in my prefix setting. 
> The easy fix for it is to add -Dinstallstyle='lib/perl5' to the
> Configure commandline in the perl build script:
>     configure: sh Configure -de -Dprefix=%%INSTALL_BASE%%
>     -Dinstallstyle='lib/perl5'
>     make: %%MAKE%%
>     install: %%MAKE%% install
>     clean: %%MAKE%% clean

> _______________________________________________
> Shipwright mailing list
> Shipwright at lists.bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/shipwright

More information about the Shipwright mailing list