On Thu, 7 Nov 2002, Ken Williams wrote:
> > Config.pm has installbin, installsitebin and installvendorbin but only
> > installscript. Dunno why.
> Okay. I'll wait a week or so for someone like Andreas or Andy
> to chime in and explain why there are no other INSTALL*SCRIPT
> entries, and if that doesn't happen I'll assume it's an error
> and I'll try to fix it.
There's no deep reason. They weren't used anywhere so metaconfig
didn't include them in Configure (and, ultimately in Config.pm.)
Since they didn't appear in Config.pm, nobody tried to use them.
When this sad circular state of affairs became apparent I posted a
Policy_sh.SH patch to fix it, but it didn't make it in time for
5.8.0.
Change #17951 incorporates this into perl-current, and 5.8.1-to-be ought
to have it as well.
> Would it be wrong to just put scripts into INSTALL*BIN? Do we
> really need to make a big distinction between executable
> binaries and executable scripts?
Some folks historically have done so. Others haven't. If there's no
*SCRIPT directory available, it probably would be a reasonable fallback to
put scripts into *BIN.
--
Andy Dougherty [EMAIL PROTECTED]
