I'm building some Perl packages that use Module::Build instead of the standard Makefile.PL and could use perlarchdir myself when I call this:
perl%type_raw[perl] Build.PL \
--install_path arch=%i/lib/perl5/%type_raw[perl]/`perl%type_raw[perl] -MConfig -e 'print $Config{archname}'` \
--install_path bin=%i/bin \
--install_path bindoc=%i/share/man/man1 \
--install_path lib=%i/lib/perl5/%type_raw[perl] \
--install_path libdoc=%i/share/man/man3 \
--install_path script=%i/bin
Could we add %{perlarchdir} to expand in .info files?Also, I noticed that $perlarchdir is determined like this:
sub get_perl_dir_arch {
..
..
if ($perlversion ge "5.8.1") {
$perlarchdir = 'darwin-thread-multi-2level';
} else {
$perlarchdir = 'darwin';
}I think a better way of doing this for future use would be just to use the Config{archname} value which generates the same values as this test, but would work regardless of what Apple does later in any future releases:
use Config:
$perlarchdir = $Config{archname};Blair
-- Blair Zajac <[EMAIL PROTECTED]> Plots of your system's performance - http://www.orcaware.com/orca/
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
