Randal --
Thanks for taking the time to check it out (and, sorry I didn't get it
right the first time). I see now where the problem was. The older
code was using the CVS revision number as the VERSION, so
the problem was deeper than just 0.009. Versions back to 0.005
have the same situation.
Therefore, I've upgraded the Perl Shell to the nicely inflated
version number of 1.7. Hopefully that will gloss over things
sufficiently. I did test my system by doing an r /Psh/ under cpan,
and it was satisfied that I am up to date.
Version 1.7 is on its way to CPAN as we speak. As before, let
me know if this doesn't make the problem go away for you...
Regards,
-- Gregor
[EMAIL PROTECTED] (Randal L. Schwartz)
01/16/2003 04:19 PM
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: Psh version number retrograde
>>>>> "gregor" == gregor <[EMAIL PROTECTED]> writes:
gregor> Randal --
gregor> Thanks for the clarification.
gregor> I've made a change I think will cure the problem, and released
gregor> version 1.1 (uploading to CPAN now). Please let me know if
gregor> this does not make things better.
No, that's still broken.
After installing 1.1, this is what it now complains:
cpan> r /Psh/
Package namespace installed latest in CPAN file
Psh 1.1 1.67
G/GR/GREGOR/psh-0.009.tar.gz
This says that even though I have Psh -- version 1.1, installed, I can
get a Psh version 1.67 by installingn psh-0.009.
Either remove psh-0.009 from the CPAN, or create a Psh module larger than
1.67 in a new release of Psh.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777
0095
<[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl
training!
