----- Original Message ----- 
From: "Ira Woodhead" <[EMAIL PROTECTED]>
To: <inline@perl.org>
Sent: Wednesday, September 20, 2006 1:26 PM
Subject: FW: Text::Scan


> > Hi all, couple of questions:
> >
> > I have no idea if this has to do with the Inline'd nature of the module,
but I thought I'd give y'all a try. :)

That's ok - though I don't think Inline is involved in the problem.

> >
> > First: The current version of Text::Scan is 0.28. But this version is
still not available as the current version on CPAN or ActiveState... after
*three weeks*.

You should ask about his on ActiveState's PPM mailing list. (You would need
to subscribe. I think http://listserv.activestate.com/mailman/mysubs will
lead you to the right place.)

>> When you "install Text::Scan" via cpan commandline the version is 0.26.

So CPAN.pm also fails to detect the existence of version of 0.28 ? Perhaps
ActiveState have failed to detect the presence of that version for the same
reason - whatever that reason happens to be :-)
I've taken a quick look at the Text-Scan-0.28 distro and can't spot anything
suspicious. Definitely worth asking about on ActiveState's PPM mailing list.

>> When you navigate to it on, say,
http://www.perl.com/CPAN/modules/by-module/Text the latest version is 0.26.
When you go to http://ppm.activestate.com/BuildStatus the version is also
0.26.
> >
> > You can find the true latest version, 0.28, only if you search:
http://search.cpan.org/search?query=text::scan .

Yes - that finds it for me, too. (And that's where I always go to find a
module.)

> >
> >
> > Second: on the ActiveState build status links for ActivePerl 6xx
(corresponding to perl 5.6), there are many "FAIL" status links which
actually lead to "All tests successful" build logs. What's up with that?

I don't know - though I've noticed the same thing myself and even asked
about it on the perl-win32-users list (hosted by ActiveState). I didn't
really get an answer - but probably the best place to ask about that would
also be on ActiveState's PPM mailing list.

Cheers,
Rob

Reply via email to