in reply to MANIFEST.SKIP and ignoring gvim .swp files

Just edit your MANIFEST file. I've never had a MANIFEST generated for me so I'm not sure what steps people are using that cause this problematic automatic population of the MANIFEST, including files that they don't want. I only want things in the MANIFEST that I intentionally want included in the module. Worst case for a huge module is "vi MANIFEST" and ":r !find" and delete some lines.

I guess the other piece is figuring out what is throwing things into your MANIFEST and stop doing that.

- tye        

  • Comment on Re: MANIFEST.SKIP and ignoring gvim .swp files (vi)

Replies are listed 'Best First'.
Re^2: MANIFEST.SKIP and ignoring gvim .swp files (vi)
by rinceWind (Monsignor) on Jul 29, 2005 at 16:00 UTC

    Digging further, it seems that the MANIFEST is not the problem. The contents of this file are always clean - no .swp files appear.

    It seems that the logic behind the scenes in MakeMaker is detecting these files when it writes the Makefile.

    I'll carry on digging.

    --

    Oh Lord, won’t you burn me a Knoppix CD ?
    My friends all rate Windows, I must disagree.
    Your powers of persuasion will set them all free,
    So oh Lord, won’t you burn me a Knoppix CD ?
    (Missquoting Janis Joplin)