>>>>> On Sun, 09 Dec 2007 00:40:37 -0800, Michael G Schwern <[EMAIL PROTECTED]> >>>>> said:
> Andreas J. Koenig wrote: >>>>>>> On Thu, 06 Dec 2007 16:20:19 -0800, Michael G Schwern <[EMAIL >>>>>>> PROTECTED]> said: >> >> > I see the missing piece is that you were using PREREQ_FATAL. Yes, that >> > did >> > move in 6.33. I didn't log why, it was part of some changes to the >> > PREREQ_FATAL docs and message. The code move doesn't look like it was >> > necessary. I guess I can move it back. >> >> I moved it in my patch because it was not overridable before. Please >> keep it overridable on the commandline. Or do me the favor to remove >> it completely. It's just plain counter to the principle rule of the >> toolchain: nobody dies, everybody drops metadata where they belong. > I'd love to just shoot it in the head, but backwards compatibility and all > that. The docs were adjusted to make it really clear to not use it. Yeah. But please, when you start supporting configure_requires, deprecate it actively. We must get rid of it. > I'll put in a test for it's overridability. Thank you! > On a related note... what's the point of CONFIGURE? I thought, maybe it could > change things after the MM object has been constructed and initialized, but it > happens before initialization and doesn't even get a copy of the object. It > seems anything you can do in CONFIGURE you can do before you call WriteMakefile. I have a very distant remembrance on CONFIGURE. I think somebody wanted to have a plug where standardized mechanisms would do what Configure does for perl. But then suddenly there was no champion to provide the standardized mechanism. Seems like another case for the chainsaw but at least it does no harm. -- andreas
