Re: INSTALLSCRIPT doesn't have 'site', 'vendor' values?

[Ken Williams]

On Tuesday, November 5, 2002, at 02:15  PM, Soren Andersen wrote:

On Tue, 05 Nov 2002 01:54:22 GMT, [EMAIL PROTECTED] (Ken Williams) wrote
in news:814B3DD1-F061-11D6-AADE-003065F6D85A@;mathforum.org:

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.

It's not so much version issues I'm concerned about, it's the separation of vendor-installed & user-installed scripts. I see that my Config.pm has these entries:

installbin='/usr/bin'
installscript='/usr/bin'
installsitebin='/usr/local/bin'
installvendorbin='/usr/local/bin'
sitebin='/usr/local/bin'
sitebinexp='/usr/local/bin'
vendorbin='/usr/local/bin'
vendorbinexp='/usr/local/bin'

On my machine, the "correct" place for user-installed executables is /usr/local/bin, but unfortunately since there's no such thing as an "installsitescript" Config entry, they get shoved into /usr/bin, where they can (and do) clobber stuff that Apple installed there.

If your Config.pm doesn't contain appropriate values for your system, OTOH, then you may want to edit it.

I believe the above entries from my Config.pm are correct, but there still doesn't seem to be any opportunity for MakeMaker to install scripts to a site-specific directory.

Schwern, I know you've spend time thinking about these issues, do you know why this is, and/or what should be done about it?

-Ken