Re: Installing a script

use ExtUtils::MakeMaker::prompt, but this should suffice

perl Makefile.PL INSTALLSCRIPT=something/custom/bin
make
make test
make install
[download]

or if you process @ARGV yourself

make  install INSTALLSCRIPT=something/custom/bin
[download]

Don't forget the PL_FILES option.

Comment on Re: Installing a script Select or Download Code

Replies are listed 'Best First'.
Re^2: Installing a script by ikegami (Patriarch) on Aug 24, 2009 at 03:32 UTC
`INSTALLSCRIPT` says where to install them (which should be set automatically by `PREFIX` and the newer & better `INSTALL_BASE`), not what to install. `PL_FILES` is completely unrelated.	[reply] [d/l] [select]
Re^3: Installing a script by Anonymous Monk on Aug 24, 2009 at 06:57 UTC
not what to install. Astroboy answered the first part of the question (EXE_FILES) himself. INSTALLSCRIPT/prompt answers the second part. PL_FILES is completely unrelated. PL_FILES is simply important; It needs to be managed. Many (even the initiated) overlook that it will install your demo.pl /example.pl /generatefoo.pl into the module tree by default. Sometimes you need to read the question closely. Thank you	[reply]
Re^4: Installing a script by ikegami (Patriarch) on Aug 24, 2009 at 07:00 UTC
`PL_FILES` is a means of specifying scripts that are executed during the installation process. For example, I used it to identify a script that compiles WSDL files into SOAP::Lite classes during installation. It has nothing to do with causing scripts to be installed or with preventing scripts from being installed. It has nothing to do with installing scripts at all.	[reply] [d/l]
Re^5: Installing a script by Anonymous Monk on Aug 24, 2009 at 07:32 UTC
Re^6: Installing a script by ikegami (Patriarch) on Aug 24, 2009 at 17:26 UTC


There's more than one way to do things
	PerlMonks