Graham Barr <[EMAIL PROTECTED]> writes:

> You may have an answer to this by now, but what I do is override
> it what I type make dist with
> 
>   make dist VERSION=2.99_12
> 
> and leave the Makefile.PL alone.

Thanks.  I'll remember this the next time.  What I ended up doing for
the HTML::Parser alphas/betas was simply to rename the file just
before uploading.

Regards,
Gisle

> On Thu, Nov 18, 1999 at 09:28:24PM +0100, Gisle Aas wrote:
> > [EMAIL PROTECTED] (Randal L. Schwartz) writes:
> > 
> > > >>>>> "tallwine" == tallwine  <[EMAIL PROTECTED]> writes:
> > > 
> > > tallwine> When building webchat-05 I got this error
> > > tallwine>         Argument "2.99_10" isn't numeric in entersub 
> > > 
> > > tallwine> I downloaded HTML-Parser-XS-2.99_12.tar.gz
> > > tallwine> In Parser.pm on line 11, if I change 
> > > 
> > > tallwine>         $VERSION = '2.99_12';
> > > tallwine> to
> > > tallwine>         $VERSION = 2.99_12;
> > > 
> > > tallwine> then install as usual. Go back to webchat and 
> > > tallwine> the error went away. 
> > > 
> > > tallwine> Bug?? Does $VERSION need to be a string?
> > > 
> > > 
> > > 2.99_12 is a normal number, equal to 2.9912.  '2.99_12' is a string
> > > numerically equal 2.99.  Clearly one is wrong. :)
> > 
> > I should probably use the number.  The problem with this is that 'make
> > dist' then produce a file called "HTML-Parser-XS-2.9912.tar.gz" which
> > will be picked up by the CPAN indexer.  I don't want that yet.  To
> > compensate I could then just rename it into some name with "2.99_12",
> > but it will still unpack as "HTML-Parser-XS-2.9912/".
> > 
> > If I force VERSION => '2.99_12' in Makefile.PL and let $VERSION =
> > 2.99_12 in Parser.pm, then the XS_VERSION_BOOTCHECK fail because it
> > compares the versions using strNE and Parser.so will not load.
> > 
> > I think this issue was discussed on perl5-porter once with regard to
> > Tk alpha releases, but don't remember any conclusions and the mailing
> > list search at http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/
> > don't respond to my searches now.

Reply via email to