On Tue, 05 Nov 2002 01:54:22 GMT, [EMAIL PROTECTED] (Ken Williams) wrote
in news:814B3DD1-F061-11D6-AADE-003065F6D85A@;mathforum.org:
> Hi,
>
> I notice the following in the MakeMaker docs (version 5.91_01):
Just FYI, ExtUtils::MakeMaker is up to current v 6.05 now. It is an easy
upgrade to do manually.
> I'm curious about why INST_SCRIPT doesn't have different values in the
> three columns. Is this why things like LWP's "HEAD" script are
> installing to /usr/bin on OS X instead of to /usr/local/bin?
I recently noticed this too. My guess is that there is an assumption
that scripts are version-independent (or will take care of version
dependency by 'requiring' some version, I s'pose). Therefore no
alternative options are built in.
I am thinking that you might need to be reminded that INST_* isn't the
final destination of the file(s). INSTALL_* is. INST_* is where in the
build directory subtrees something will be put when one does `make'.
The perldoc for mm v6.05 says:
The INSTALL... macros in turn default to their %Config
($Config{installprivlib}, $Config{installarchlib}, etc.)
counterparts.
You can check the values of these variables on your system
with
perl '-V:install.*'
Arguing INSTALL_SCRIPT directly on the cmdline would seem to be the most
direct mechanism for determining where the script installs.
> In my case, I'm writing a prompt like the following, but I suspect
> there's a better way to get the destination directory so that the user
> could override it with INST_SCRIPT=/foo or something. Is there some
> way to get this value from MakeMaker instead of from Config?
>
> if (prompt("Do you want to install the command-line script
> 'categorizer' ".
> "to $Config::Config{installscript}?", 'n') =~ /^y/i) {
> $options{EXE_FILES} = [qw(eg/categorizer)];
> }
>
Yeah, i don't know. There's no such thing as a persistent 'cache' of
installation default values kept by MakeMaker separately from the
Config.pm (except for a per-user "MyConfig.pm" IIRC, RTFM). You've read
and understood what to use PREFIX for? It seems to me that most people
need to use PREFIX to set a non-standard prefix-location. If your
Config.pm doesn't contain appropriate values for your system, OTOH, then
you may want to edit it. (I am avoiding commenting that it's odd for it
not to have appropriate values, because I come from Win32 which is where
this is the norm rather than a bizarre deviation).
All or any of my helpfully-intended comments may be a little or grossly
wrong. I just joined this Mailing List. But hopefully somehow i will
have helped.
Best,
Soren A
--
http://fastmail.fm - Same, same, but different...
