Skip Menu |

This queue is for tickets about the CPAN-Changes CPAN distribution.

Report information
The Basics
Id: 87045
Status: rejected
Priority: 0/
Queue: CPAN-Changes

Owner: Nobody in particular
Requestors: victor [...]

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

Subject: Why it is not possible to allow changelogs with different filenames?
Download (untitled) / with headers
text/plain 727b
subj. i.e. CHANGES and ChangeLog and Changelog several words in defense of "ChangeLog": 1) CPAN and MetaCPAN process it well. example: 2) Wiki Article exists for ChangeLog, not for changes: 3) CPAN distributions are not necessary related to Perl and made for Perl users, App:: namespace introduce software targeting for non-programmers also, non necessary distributed over CPAN-only. So CPAN statistics for use of Changes vs CHANGES vs ChangeLog not necessary relevant. Debian, for example, prefers "debian/changelog" file related RT#67527
Download (untitled) / with headers
text/plain 468b
Le 2013-07-19 13:12:24, vsespb a écrit : Show quoted text
> subj. > > i.e. CHANGES and ChangeLog and Changelog > > several words in defense of "ChangeLog":
I'm not the author of the specification. And I also admit that I disagree on some But the point of a specification is to try to unify things. And following the Changes specification is not mandatory to make your CPAN module work. So you are free to not follow the spec. -- Olivier Mengué -
Download (untitled) / with headers
text/plain 364b
Using the name Changes is the convention for CPAN, so it makes sense to follow that. But while the files are described as Changes files, there is nothing in the code or the spec that requires that filename. Test::CPAN::Changes defaults to checking Changes files, but changes_file_ok can be used to test an arbitrary file. So I don't see anything to change here.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to