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

The rule is simple: what can't be generated belongs to version control. What can be generated doesn't belong there.

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
[download]

Comment on Re^3: Making the CPAN/GitHub updating process painless Download Code

Replies are listed 'Best First'.
Re^4: Making the CPAN/GitHub updating process painless by nysus (Parson) on Dec 16, 2017 at 18:37 UTC
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	[reply]
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]