In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Iain Truskett) wrote:
> > The only thing I would want to avoid is pulling over something if you > > have it already & deleting older packages as new ones come along. > > The former, it does. The latter, it doesn't. Can I blame the way that > nobody seems to be able to decide on what a version nubmer should be? =) > (Just been selectively upgrading RPMs, and the sheer ridiculousness of > some of thee verison numbers is something to be seen.) something I myself noticed when building my modulereport script. (posted it in the perl.scripts forum here on perl.org, just recently, for review and comment, as I intend to post it to CPAN's scripts section. you may find it useful as an adjunct to what you've already got there.) I too had a hard time believing how some of the internal versioning is done. crazy regex and substr reductions of long version strings instead of a simple package::VERSION = nn.nn.nn; *bemused headscratching* print pack "H*", "4a75737420416e6f74686572204d61635065726c204861636b65722c0d"; -- Scott R. Godin | e-mail : [EMAIL PROTECTED] Laughing Dragon Services | web : http://www.webdragon.net/ It is not necessary to cc: me via e-mail unless you mean to speak off-group. I read these via nntp.perl.org, so as to get the stuff OUT of my mailbox. :-)
