teikweidi has asked for the wisdom of the Perl Monks concerning the following question:

I have an existing structure of modules that live and work well and are installed via one Makefile. I want to add to that structure new dirs/mods (i have added perl module shells according to the needed Object Oriented heirarchy). While I flush out the new dirs/mods, I want to be able to bring each new module live as I finish it (add it via the make process). I viewed a few messages in the Archives that suggested using a MANIFEST.SKIP file. I edited the file and included regexes for the dirs/mods that I wanted left out. I ran:

$>perl Makefile.PL
$>make manifest
$>make realclean

I noticed that this gave me the correct MANIFEST file with only the dirs/mods that I want to install via make, I also saw confirmation via STDOUT that the modules were being excluded from MANIFEST. However, when I later did:

$>perl Makefile.PL
$>make

I noticed via STDOUT and also in my Makefile that the mods I wanted to exclude are still being prepared.

Any help or comments would be much appreciated. Thank you.
  • Comment on Understanding MANIFEST and MANIFEST.SKIP to avoid making dirs/modules.

Replies are listed 'Best First'.
Re: Understanding MANIFEST and MANIFEST.SKIP to avoid making dirs/modules.
by PodMaster (Abbot) on May 27, 2003 at 00:47 UTC
    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
    Read more... (427 Bytes)
    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.

[reply]
[d/l]
      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]
      Good Day PodMaster,
      Thank you for the good advice and direction. I appreciate it.
[reply]
Re: Understanding MANIFEST and MANIFEST.SKIP to avoid making dirs/modules.
by fglock (Vicar) on May 27, 2003 at 14:18 UTC

    Check that you have a MANIFEST.SKIP entry in MANIFEST.

    If you don't, MANIFEST.SKIP will not be entered in the distribution archive file.

[reply]

Back to Seekers of Perl Wisdom