in reply to What is ignore.txt

What is a xt directory for? Can I ignore or delete it?

xt is for eXtra Tests - tests which are not run as a matter of course can go in here. You may well not have any so you can happily either ignore or delete. It's easy to re-create if you decide you want it later on.

For slightly later, once I've built the module, should I delete the blib directory before make dist?

make clean should take care of that for you - no need to do it by hand.

I had to add use lib 'lib'; to the test files to make the tests use the right version of the module.

How are you running the tests? make test should use this lib path (actually blib/lib) by default. prove has a -l option which takes care of that for you also.

PS. to answer the question in the title, ignore.txt is a generic version control ignore list. This is detailed in the POD for Module::Starter.

🦛

Replies are listed 'Best First'.
Re^2: What is ignore.txt
by Bod (Parson) on Jun 08, 2023 at 18:32 UTC

    Thanks you hippo - that's got me much further :)

    ignore.txt is a generic version control ignore list. This is detailed in the POD for Module::Starter

    Well...it only seems to say it creates it by default.

    That doesn't help with the error I'm getting 

    # The following files are not named in the MANIFEST file: C:\Users\use
+r\Perl\AI-Embedding\AI-Embedding\ignore.txt

    [download]
    As I'm not using any kind of version control (I don't think I am), should I get rid of the file or do I need to add it to the manifest file?

[reply]
[d/l]
[select]

      I strongly second hippo's recommendation that you version control your code. It seems a bit over the top for a lone shark developer to do that, but if you commit frequently it can save you from brain farts, cats, dogs and small children interacting with your keyboard in unfortunate ways, acts of nature, hard drive failures, ...

      Really, spin up a git repo somewhere in the cloud and git committing. Not tomorrow, or the day after -today is the day to do it! (Says he who has been bitten more than once!)

      Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
[reply]

        I agree with that, too. Decentralized version control (mercurial in my case) has saved me countless times. I run a setup where commits are automatically synced to multiple systems in different locations. Even a fire or bankruptcy of a cloud service leaves enough intact copies to continue "business as usual".

        PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP
[reply]
[reply]

      You can also add the file to MANIFEST.SKIP, which is the ignore list. Every file or directory in your development directory should be either in MANIFEST (and be shipped) or in MANIFEST.SKIP.

[reply]
[d/l]
[select]

      If you are not using it, just get rid of it. I would never ship any file relating to version control in the dist so would not add it to the MANIFEST. The only files needed in the dist are those which a user requires in order to build, test and install the dist.

      That said, it will be worth your while to look into using version control sooner or later. You've started using git for other tasks so maybe you could think about putting this code into a git repo also?

      🦛

[reply]

In Section Seekers of Perl Wisdom