Skip Menu |

This queue is for tickets about the Test-CheckChanges CPAN distribution.

Report information
The Basics
Id: 46976
Status: resolved
Priority: 0/
Queue: Test-CheckChanges

People
Owner: Nobody in particular
Requestors: user42 [...] zip.com.au
Cc:
AdminCc:

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



Subject: suggest plain "Version N" format
Date: Tue, 16 Jun 2009 09:47:40 +1000
To: bug-Test-CheckChanges [...] rt.cpan.org
From: Kevin Ryde <user42 [...] zip.com.au>
I've been using a changes line like Version 6, June 2009 and similar can be found in a few dists, eg. Carp::Clan Version 6.00 17.02.2008 Each is at the start of a line, which might be important for avoiding something discussing an unrelated "version 123" in the ordinary text part of an entry. Could this rate as "not horrid" to incorporate perhaps per below?
--- CheckChanges.pm.orig 2009-06-16 09:12:46.000000000 +1000 +++ CheckChanges.pm 2009-06-16 09:30:46.000000000 +1000 @@ -205,6 +205,16 @@ } else { push(@not_found, "$1"); } + } elsif (/^Version ([\d.]+)($|[:,[:space:]])/) { +# Plain "Version N" + $mixed++ if $type and $type != 4; + $type = 4; + if ($version eq $1) { + $found = $_; + last; + } else { + push(@not_found, "$1"); + } } } close(IN) or die "Could not close ($change_file) file";
This Changefile format will be in the version 0.08 release.