2010/2/16 Alberto Simões <al...@alfarrabio.di.uminho.pt>:
> OK, because there isn't a $builder->binary_files option or a
> $builder->executable_files option :P
Long, sordid history here. This is more or less correct as a summary of it:
* Used to have a 'scripts' property that defaulted to the 'scripts'
directory in the distribution directory
* 'scripts' property was renamed to 'script_files'
* 'script_files' changed to default to 'bin' directory in the
distribution directory
* 'script_files' contents copied to blib/script
* things in blib/script installed to a location depending on
installdirs or install_base:
'core' => $Config{installscript}
'site' => $Config{installsitescript} || $Config{installsitebin} ||
$Config{installscript}
'vendor' => $Config{installvendorscript} ||
$Config{installvendorbin} || $Config{installscript}
or for install_base => "$installbase/bin"
Clear as mud, right?
So what you need to do is probably follow the "Adding new file types
to the build process" recipe in the Module::Build::Cookbook and add a
"bin" type with a process_bin_files that puts things in blib/bin --
then you'll get whatever default installdirs/install_base behavior is
normal for "bin" type files. E.g. $Config{installsitebin}
-- David
