Re: how to release XS dists from ./dist

On Mon, Jan 11, 2016 at 9:26 AM, Ricardo Signes
<perl.p5p@rjbs.manxome.org> wrote:
> I've been trying to eliminate unneeded extra repositories used upstream-blead
> dists.  I want it to be easy to keep perl5.git as the only repo needed for
> making a CPAN release, so that it's as easy and uniform as possible, and can be
> done, perhaps, by release managers, taking us further into the golden years of
> perl release simplification.
>
> I hit a snag with PathTools.  I suspect it's something simple, but I've never
> dealt with it, so I'd appreciate any advice, because for me it ain't easy.
> (I hit this snag while adding "Changes," which led to the brief manifest.t
> failure.  I was under pressure to get the new release out for the CVEs.)
>
> PathTools wants ppport.h to ship with it.  It keeps this in its GitHub repo,
> and releases make from there are hunky dory.  When I try to release from blead,
> it fails, and obviously keeping another copy of ppport.h in its repo would be
> no good.
>
> If somebody could sort this out, they would be heroes, and I would be dancing
> in the street.

I think the following will work but I'm not where I can test it out
properly at the moment.

1.) Build perl in your perl.git repository.  That gets you a ppport.h
in dist/PathTools.
2.) Get into the module directory and clean up the build products that
should not go in MANIFEST. This leaves ppport.h since that came from
an external source:

    cd dist/PathTools
    make clean

3.) Build yourself a MANIFEST:

   perl -MExtUtils::Manifest=mkmanifest -e 'mkmanifest()'

4.) Then just:

    perl Makefile.PL
    make dist

• how to release XS dists from ./dist by Ricardo Signes
• Re: how to release XS dists from ./dist by Craig A. Berry