Re: Understanding MANIFEST and MANIFEST.SKIP to avoid making dirs/modules.

That should've taken care of it, what does you MANIFEST.SKIP file look like? Which version of ExtUtils::MakeMaker do you have? Here's what mine looks like

^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$
\~$
[download]

What's the directories you're trying to avoid?

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.

Comment on Re: Understanding MANIFEST and MANIFEST.SKIP to avoid making dirs/modules. Download Code

Replies are listed 'Best First'.
Re: Re: Understanding MANIFEST and MANIFEST.SKIP to avoid making dirs/modules. by teikweidi (Novice) on May 27, 2003 at 15:31 UTC
Well, had I been logged in, PodMaster would have seen my gratitude, but I see that the thank you issued as Anonymous Monk is apparent to nobody except myself, so: Thank your PodMaster, I appreciate your excellent advise, and have a good day.	[reply]
Re: Re: Understanding MANIFEST and MANIFEST.SKIP to avoid making dirs/modules. by Anonymous Monk on May 27, 2003 at 15:21 UTC
Good Day PodMaster, Thank you for the good advice and direction. I appreciate it.	[reply]