Skip Menu |

This queue is for tickets about the ExtUtils-MakeMaker CPAN distribution.

Report information
The Basics
Id: 9452
Status: resolved
Worked: 1 min
Priority: 0/
Queue: ExtUtils-MakeMaker

People
Owner: Nobody in particular
Requestors: jc [...] unser.net
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)



Subject: Parsing of $VERSION fails for certain packages
Certain packages (e.g. HTML::WebMake::HTMLCleaner) don't contain a $VERSION of their own but code like # this parameter is not supported in earlier versions if ($HTML::Parser::VERSION >= 3.00) { my $val = '==BOOL_TRUE=='; eval ' $self->boolean_attribute_value ($val); $BOOL_ATTR_VALUE = $val; '; } ExtUtils::MM_Unix produces error messages like this one if checking for a VERSION (e.g. from inside CPAN.pm with the "r" command): Could not eval ' package ExtUtils::MakeMaker::_version; no strict; local $HTML::Parser::VERSION; $HTML::Parser::VERSION=undef; do { if ($HTML::Parser::VERSION >= 3.00) { }; $HTML::Parser::VERSION ' in /usr/lib/perl5/site_perl/5.8.0/HTML/WebMake/HTMLCleaner.pm: Missing right curly or square bracket at (eval 541) line 10, at end of line syntax error at (eval 541) line 10, at EOF Attached is a patch which solves this. A much better solution would be an applied standard for specifying package versions, of course.
--- MM_Unix.pm 2004-12-15 13:01:32.000000000 +0100 +++ MM_Unix.pm.orig 2005-01-05 22:58:42.000000000 +0100 @@ -3042,6 +3042,7 @@ next if $inpod || /^\s*#/; chop; next unless /(?<!\\)([\$*])(([\w\:\']*)\bVERSION)\b.*\=/; + next if /^\s*(if|unless)/; my $eval = qq{ package ExtUtils::MakeMaker::_version; no strict;
Thanks, applied. Better late than never?
Subject: Re: [rt.cpan.org #9452] Parsing of $VERSION fails for certain packages
Date: Fri, 17 Apr 2009 15:31:28 +0200
To: Michael G Schwern via RT <bug-ExtUtils-MakeMaker [...] rt.cpan.org>
From: Juergen Christoffel <jc [...] unser.net>
On Wed, Apr 08, 2009 at 11:03:02PM -0400, Michael G Schwern via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=9452 > > > Thanks, applied. Better late than never?
Sure, better late than never. Altough I switched to using the Debian Packages mainly and wasn't even aware that the ticket was still open. Thanks, JC -- Ich bin keiner von uns. -- Hans Magnus Enzensberger
I don't believe in closing tickets just because they're old. Ciao.
From: victor [...] vsespb.ru
On Fri Apr 17 20:53:55 2009, MSCHWERN wrote: Show quoted text
> I don't believe in closing tickets just because they're old. Ciao.
I am getting same (or similar) problem with ExtUtils-MakeMaker 6.68 (cpan "r" command, too) AnyDBM_File 1.00 1.01 RJBS/perl-5.18.0.tar.gz App::MtAws::CheckLocalHashCommand undef 0 VSESPB/App-MtAws-0.962.tar.gz Could not eval ' package ExtUtils::MakeMaker::_version; no strict; BEGIN { eval { # Ensure any version() routine which might have leaked # into this package has been deleted. Interferes with # version->import() undef *version; require version; "version"->import; } } local $JSON::XS::VERSION; $JSON::XS::VERSION=undef; do { my $meta_coder = ($JSON::XS::VERSION >= 1.4) ? }; $JSON::XS::VERSION; ' in /usr/local/share/perl/5.14.2/App/MtAws/MetaData.pm: syntax error at (eval 225) line 17, at EOF Could not eval ' package ExtUtils::MakeMaker::_version; no strict; BEGIN { eval { # Ensure any version() routine which might have leaked # into this package has been deleted. Interferes with # version->import() undef *version; require version; "version"->import; } } local $JSON::XS::VERSION; $JSON::XS::VERSION=undef; do { my $meta_coder = ($JSON::XS::VERSION >= 1.4) ? }; $JSON::XS::VERSION; ' in /usr/local/share/perl/5.14.2/App/MtAws/MetaData.pm: syntax error at (eval 226) line 17, at EOF CGI 3.52 3.63 MARKSTOS/CGI.pm-3.63.tar.gz Compress::Zlib 2.033 2.061 PMQS/IO-Compress-2.061.tar.gz
RT-Send-CC: victor [...] vsespb.ru
I've merged Victor's pull request https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker/pull/62 into EUMM repository and released development version v6.69_05 to CPAN. Many thanks.
This issue is now resolved with the release of 6.70 Many thanks.