in reply to Re^3: Issues with first module build
in thread Issues with first module build

Not a lot of info:

perl t/manifest.t 1..0 # SKIP Author tests not required for installation

Addendum: More info

export RELEASE_TESTING=1; perl t/manifest.t 1..1 not ok 1 # Failed test at /usr/local/share/perl/5.30.0/Test/CheckManifest.pm +line 190. # got: 0 # expected: 1 # The following files are not named in the MANIFEST file: /home/leam/t +mp/test_module_starter/MANIFEST.SKIP, /home/leam/tmp/test_module_star +ter/MANIFEST.SKIP.bak # MANIFEST: /home/leam/tmp/test_module_starter/MANIFEST # Looks like you failed 1 test of 1.

Chronicler: The Domici War (domiciwar.net)

General Ne'er-do-well (github.com/LeamHall)

Replies are listed 'Best First'.
Re^5: Issues with first module build
by hippo (Archbishop) on Jan 05, 2021 at 10:38 UTC

    Looks like you need to add ^MANIFEST\. to the contents of MANIFEST.SKIP.


    🦛

Re^5: Issues with first module build
by stevieb (Canon) on Jan 05, 2021 at 16:20 UTC

    It looks like distcheck isn't honouring the MANIFEST.SKIP file. Let ./Build test be enough. The t/manifest.t tests check the MANIFEST anyway, and it appears it does so properly.

    Just add MANIFEST.SKIP to MANIFEST as hippo said, or do a ./Build manifest.

Re^5: Issues with first module build
by stevieb (Canon) on Jan 05, 2021 at 16:24 UTC

    I misread the code when I wrote the below. Now, I'm unsure why MANIFEST.SKIP isn't being used. Nonetheless, my above post stands.

    Module::Build::distcheck() in a round about way has this line: $self->_check_manifest_skip unless $self->invoked_action eq 'distclean';. That means the MANIFEST.SKIP file is not being used when the distcheck command is run.

    Add MANIFEST to the MANIFEST.SKIP as hippo suggested, and just let ./Build test be enough... it verifies whether MANIFEST is up-to-date with the t/manifest.t file anyway.