Skip to content

Conversation

jkeenan
Copy link
Contributor

@jkeenan jkeenan commented May 12, 2025

Git should be aware of MANIFEST and MANIFEST.SKIP. Once your code is on github.com, someone may fork it and want to run it through the typical 'perl Makefile.PL -- make -- make test' cycle. Save them the trouble of calling 'make manifest' unless they've modified either of those files.

Git should be aware of MANIFEST and MANIFEST.SKIP.  Once your code is on
github.com, someone may fork it and want to run it through the typical
'perl Makefile.PL -- make -- make test' cycle.  Save them the trouble of
calling 'make manifest' unless they've modified either of those files.
@haarg
Copy link
Contributor

haarg commented May 12, 2025

A MANIFEST file isn't needed to run any of perl Makefile.PL, make, make test, or even make install. It is only used for make dist. It is a generated file only needed when making releases, and including it in the repo is generally just noise.

@khwilliamson
Copy link
Contributor

Any objections to my closing this request without merging?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants