- Original Message -
From: Michael G Schwern [EMAIL PROTECTED]
To: Perl 5 Porters [EMAIL PROTECTED]; makemaker@perl.org; John
Peacock [EMAIL PROTECTED]
Sent: Monday, July 02, 2007 1:56 PM
Subject: [ANNOUNCE] ExtUtils::MakeMaker 6.35
One little niggle on my Win32 build (perl 5.8.8) -
Sisyphus wrote:
I guess this is because version.pm wants to stringify '1.03' as '1.030'
- but, apart from taking a quick look at 'perldoc version', I've done
nothing to verify that guess :-)
Upgrade to the latest version.pm release and you will be OK. I was
pressured by folks on p5p to not
On Sun, Jul 01, 2007 at 08:56:55PM -0700, Michael G Schwern wrote:
A quick fix to the tests and a new feature!
I caved in. MM-parse_version() will now try to load version.pm before
checking the $VERSION of a module. This allows this to work:
our $VERSION = qv(1.2.3);
Of course,
Sisyphus wrote:
I don't think version.pm is in strict.pm (and I don't think it needs to be
for the error to occur):
Are you saying version.pm had some sort of code tentacles that effected every
instance of $VERSION even if you did $VERSION = '1.23'?
What version of version was it that caused
I had the same error today on Solaris 8. Firewalls prevented me reporting
it. I'll show my ignorance here. Isn't it just a matter of ammending
MakeMaker to require a certain version of version.pm or better? Or do we
have some sort of circular dependancy problem?
-Original Message-
From:
Todd Rinaldo wrote:
I had the same error today on Solaris 8. Firewalls prevented me reporting
it.
What version of version.pm were you using?
I'll show my ignorance here. Isn't it just a matter of ammending
MakeMaker to require a certain version of version.pm or better? Or do we
have some
- Original Message -
From: Michael G Schwern [EMAIL PROTECTED]
To: Sisyphus [EMAIL PROTECTED]
Cc: makemaker makemaker@perl.org
Sent: Tuesday, July 03, 2007 12:01 PM
Subject: Re: [ANNOUNCE] ExtUtils::MakeMaker 6.35
Sisyphus wrote:
I don't think version.pm is in strict.pm (and I don't
