Re^4: Making the CPAN/GitHub updating process painless

OK, had to mull that over. So answer is "no, those files should not go there." Sounds like a good rule to follow.

$PM = "Perl Monk's";
$MCF = "Most Clueless ~~Friar~~ ~~Abbot~~ ~~Bishop~~ ~~Pontiff~~ ~~Deacon~~ ~~Curate~~ Priest";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

Comment on Re^4: Making the CPAN/GitHub updating process painless

Replies are listed 'Best First'.
Re^5: Making the CPAN/GitHub updating process painless by shmem (Chancellor) on Dec 16, 2017 at 20:25 UTC
Makefile, MYMETA.yml and MYMETA.json are generated by `perl Makefile.PL` and MANIFEST can be (re-)created using the created Makefile issuing `make manifest`, so you can skip those files, although a proper MANIFEST serves to check the distribution for completeness. So it is probably a good idea to update MANIFEST after adding files and push that, too. perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: Making the CPAN/GitHub updating process painless
by shmem (Chancellor) on Dec 16, 2017 at 20:25 UTC

Makefile, MYMETA.yml and MYMETA.json are generated by perl Makefile.PL and MANIFEST can be (re-)created using the created Makefile issuing make manifest, so you can skip those files, although a proper MANIFEST serves to check the distribution for completeness. So it is probably a good idea to update MANIFEST after adding files and push that, too.

perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'

[reply]
[d/l]
[select]