in reply to Re: Making the CPAN/GitHub updating process painless
in thread Making the CPAN/GitHub updating process painless

OK, got it working. Is it a good idea to release the Manifest, yaml and other such files for cpan to github? I see it done all the time but seems to just get in the way.

$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^2: Making the CPAN/GitHub updating process painless

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

      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]

        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]

In Section Seekers of Perl Wisdom