Todd Rinaldo

FYI porting/manifest.t is failing right now.

> > Thank you; do we need to repeat for new pushes or will it start up automatically? > > I suspect we will need to repeat, since for the...

> @toddr For the record, it doesn't appear that a force push automatically restarts the workflow. I'm assuming that it's because I'm still a first-time contributor. Can any kick it...

I also see a failure on porting/authors.t A failure on this run aborts the other jobs. https://github.com/Perl/perl5/runs/7992394173?check_suite_focus=true

> @iabyn / @demerphq - I'll merge this within a few days unless you'd prefer me to hold off for further review. Apologies @richardleach please rebase and force push to...

@Leont does that mean you're looking at this issue then?

OK. I’m gonna put your name on it so we know who is involved

Wouldn't this get rid of dog-fooding? what is the negative of using ppport.h in core builds? we already generate the file during builds.

> All of the other modules in dist/ and many in cpan/ already exclude ppport.h when building in core. So if this is wrong, most XS dists in core are...

Would it be possible to move where -x is used to allow -x and --perl to work together?