Re: Issues with first module build

Issue 1: why are those testfiles under t/lib ? why not just under t/ ?

Issue 2: ~~replace backslashes with slashes: perl -pi.bak -e 's{\\}{/}g' MANIFEST.SKIP and ./Build disttest succeeds.~~ - wrong, see below

perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'

Comment on Re: Issues with first module build Select or Download Code

Replies are listed 'Best First'.
Re^2: Issues with first module build by kcott (Archbishop) on Jan 05, 2021 at 02:27 UTC
"... `s{\\}{/}g` ..." That will change the boundary assertion (`\b`) into `/b`. None of the filenames contain `/bbookbot-`. — Ken	[reply] [d/l] [select]
Re^3: Issues with first module build by shmem (Chancellor) on Jan 05, 2021 at 02:54 UTC
That will change the boundary assertion (\b) into /b. er... right. I didn't check with the original MANIFEST.SKIP - which is just fine on my box for `./Build disttest` So all above from my part wrt Issue 2 is wrong. Sorry. Must be something else... perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'	[reply] [d/l]
Re^2: Issues with first module build by Leitz (Scribe) on Jan 05, 2021 at 00:57 UTC
Issue 1: Because I tend to have a lot of tests, and I like to keep them orderly. Issue 2: Everything in the rest of the MANIFEST.SKIP file was created by the initial build process. I just duplicated that. Running the perl command you gave did not fix the error. I'm still working on it. :) Chronicler: The Domici War (domiciwar.net) General Ne'er-do-well (github.com/LeamHall)	[reply]
Re^3: Issues with first module build by shmem (Chancellor) on Jan 05, 2021 at 01:00 UTC
On windows, quoting is different, sorry. I have a Linux box. `perl -pi.bak -e "s{\\}{/}g" MANIFEST.SKIP` [download] perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'	[reply] [d/l]