On Thu, Jan 02, 2003 at 10:17:16AM -0500, [EMAIL PROTECTED] wrote:
> Craig Berry wrote in reply to me:
>
> !>but I am not too certain about which MakeMaker is in perl@18376
> !
> !I'm not either, but whatever it is it's going to change. But is
> !Constant.t part of MakeMaker? I don't see it in the current snapshot.
>
> Well one thing to do is:
>
> % grep '^\$VERSION' lib/ExtUtils/MakeMaker.pm
> $VERSION = "6.03";
>
> Michael's announcement dated 19-DEC-2002 was for MakeMaker
> "6.06_01 alpha", so the perl distribution has yet to catch up.
> Perhaps he could comment on the process of putting his work into
> bleedperl (CCed).
ExtUtils::Constant is not part of the ExtUtils::MakeMaker distribution.
That's Nick Clark's baby.
6.06 won't be going into bleadperl until Win32 dmake and VMS work, no point
in breaking all of perl when we can do it as a module. Its currently
blocked waiting for VMS fixes.
> For what it is worth I note a difference between a Solaris
> built Makefile and a VMS built descrip.mms
> file as follows:
<snip>
If this is a discussion about clean moving Makefile -> Makefile.old and
whether VMS's clean target should mirror with Descrip.MMS ->
Descrip.MMS_old, I can say two things.
1) I don't know the logic behind why clean moves the Makefile.
2) Unless there's a reason otherwise, VMS's clean target should
logically match what everyone else does.
Which means that if Unix's clean moves the Makefile, VMS should as well.
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Milk may build strong bones, but adhesives are cement for the mind.
http://www.goats.com/archive/990103.html
