Skip Menu |

This queue is for tickets about the dmake CPAN distribution.

Report information
The Basics
Id: 49539
Status: resolved
Priority: 0/
Queue: dmake

People
Owner: Nobody in particular
Requestors: adamk [...] cpan.org
Cc:
AdminCc:

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



Subject: ChangeLog out of date
The change log for this distribution stopped being updated in February 2008, and needs to be updated to we can tell what changed in new releases.
The dmake-4.12-20090907-SHAY release is a binary release of the latest version of the dmake source available from its current maintainers (OpenOffice.org). I've been waiting (and chasing after them) for quite a while to get 4.12 "officially" released and uploaded on http://tools.openoffice.org/dmake/ but so far this still hasn't happened. I therefore decided to release the latest source available in SVN at the location given in the README.TXT file (which is identical to the version in OpenOffice 3.1.1, and is what I believe should be made available as the "official" 4.12 at the above location). This version has a number of changes in it which *are* detailed in the ChangeLog: diff that with the ChangeLog in dmake-4.11-20080107-SHAY to see (at least some of) what's new. In particular, it contains a fix for CPAN RT #32220, which is one reason that I wanted to get a new release out. In fact, the ChangeLog may very well be up-to-date, i.e. there may not have been any changes since the last entry in it (2008-02-26). The SVN log for the above location shows some activity later than that, but it virtually all appears to be integrations into different development streams. In any case, the binary builds that I've put on CPAN simply contain the ChangeLog from the source that they are built from. I don't modify the ChangeLog at all because I very rarely have anything to do with the changes in it, so I'm not in a position to fill in the blanks if there are any. I will continue to chase OOo for an "official" 4.12, and I'll also try to check that the ChangeLog is indeed up-to-date.