^MANIFEST\. ^Makefile$ ^blib/ ^MakeMaker-\d ^pm_to_blib$ \.def$ \.bs$ \.o$ \.obj$ \.def$ \.old$ \.c$ \.lib$ \.exe$ \.la$ \.a$ \.lnk$ \.lai$ \.lo$ \.log$ \.i$ \.s$ \.tar$ \.gz$ \.zip$ \.xsc$ \.tds$ ^pod2htm \.html$ \.bak$ \~$
update: When developing/testing modules, it's best to do a `make dist', and then unpack the resulting distribution someplace other than the current working directory, and then try to make it.
Apparently, MANIFEST and MANIFEST.SKIP are consulted during make dist (among a few others), but not make. Sticking whatever dirs you were trying to hide under `t' should work %100. A `lib' has always been special to MakeMaker. MakeMaker also checks for $cwd/*/Makefile.PL, and runs those ($cwd -- current working directory).
|
MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy. |
In reply to Re: Understanding MANIFEST and MANIFEST.SKIP to avoid making dirs/modules.
by PodMaster
in thread Understanding MANIFEST and MANIFEST.SKIP to avoid making dirs/modules.
by teikweidi
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |