Skip to content

Patched tarball name #1

Description

@schwern

Currently the README says the distribution should be:

authors/id/D/DC/DCONWAY/Foo-Bar-PATCHED-1.20.tar.gz

That is incorrect, in so far as CPAN conventions for parsing an archive name goes. That reads as "The Foo-Bar-PATCHED distribution, version 1.20, released by DCONWAY". It's a different distribution, with the wrong author, and it doesn't sort higher than the one we're patching.

Since this archive is intended as a release of the Foo-Bar distribution, only the version number should be altered. There's some considerations...

  • It should be unique
  • It should clearly identify itself as a non-author official patch
  • A future, official, stable release of Foo-Bar should not blow over it
  • It should sort higher than the release it is patching

Can't do Foo-Bar-1.20-PATCHED because that doesn't parse and even if it did 1.20-PATCHED isn't a sortable version.

One possibility is to make the patched version an alpha release.

Foo-Bar-1.20_001.tar.gz

Another is to add an extra dot.

Foo-Bar-1.020.1.tar.gz

Or

Foo-Bar-1.200001.tar.gz

It's possible the author will put out a matching release of their own which brings us to the next issue, the uploads should appear as the CPAN id of the person doing the patch. NOT the original releaser. The "author" part of the path on CPAN is really the "releaser" field, who made that release.

authors/id/M/MS/MSCHWERN/Foo-Bar-1.20.1.tar.gz

Those things should make for a safer Pinto/CPAN overlay.

  • Leave the distribution name as is, only change the version number
  • Use a normal version number
  • Use a higher version number than the one you're patching
  • Use the patch author's CPAN id, not the original release author

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions