Re: All MakeMaker HTMLifying functionality is going away
On Fri, Nov 08, 2002 at 12:55:01PM -0500, Andy Dougherty wrote:
We'd give you one if we had a clue what it should be.
Yeah, I don't expect it to be solved. Besides, the Great Convert Everything
To HTML Craze is mercifully over.
Now let's talk $Config{installyamldir}... ;)
--
Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/
Perl Quality Assurance [EMAIL PROTECTED] Kwalitee Is Job One
That's what Jagulars always do, said Pooh, much interested. They call
'Help! Help!' and then when you look up they drop down on you.
Re: INSTALLSCRIPT doesn't have 'site', 'vendor' values?
On Thursday, November 7, 2002, at 05:56 PM, Andreas J. Koenig wrote: On Thu, 7 Nov 2002 13:18:17 +1100, Ken Williams [EMAIL PROTECTED] said: 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. Sorry, I have no answer to this one. 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? The reason for 'script' being separated from 'bin' was that you can share scripts between architectures but usually cannot share binaries. If people actually make use of this distiction, nobody knows. It sounds like the kind of thing someone's going to be using somewhere, so it probably shouldn't get completely broken. If I were to fix this, I think there would be a few parts to it: 1) MakeMaker should try to determine a better place to put scripts (by guessing) 2) EU::Install should honor that 3) Config.pm should have INSTALLSITESCRIPT and INSTALLVENDORSCRIPT entries so MM doesn't have to guess In practice, I don't think any 'hints' files (in 5.8, anyway) have INSTALLBIN and INSTALLSCRIPT different, so it's probably pretty safe to guess from INSTALL*BIN, I think. Then I have to figure out how to cooperate/repeat with Module::Build. -Ken
Re: INSTALLSCRIPT doesn't have 'site', 'vendor' values?
On Thu, Nov 07, 2002 at 07:54:18PM +1100, Ken Williams wrote: It sounds like the kind of thing someone's going to be using somewhere, so it probably shouldn't get completely broken. The two likely candidates are AFS users, who routinely shuffle files around all over the place and use obscure features of MM, and module repackagers (ie. Redhat, Debian, etc...) who need to seperate out architecture dependent vs independent bits. If I were to fix this, I think there would be a few parts to it: 1) MakeMaker should try to determine a better place to put scripts (by guessing) Should be possible using the same tricks as the other iffy variables in init_INSTALL(). 2) EU::Install should honor that It'll do that automaticly. It doesn't know anything about the INSTALL* variables, it just gets fed paths. ExtUtils::Install is really just a glorified copy command like GNU install. 3) Config.pm should have INSTALLSITESCRIPT and INSTALLVENDORSCRIPT entries so MM doesn't have to guess We'll still have to guess for all older versions, so no code savings there. :( In practice, I don't think any 'hints' files (in 5.8, anyway) have INSTALLBIN and INSTALLSCRIPT different, so it's probably pretty safe to guess from INSTALL*BIN, I think. Then I have to figure out how to cooperate/repeat with Module::Build. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ Perl Quality Assurance [EMAIL PROTECTED] Kwalitee Is Job One You see, in this world there's two kinds of people. Those with loaded guns, and those who dig. Dig. -- Blondie, The Good, The Bad And The Ugly
