MANIFEST.SKIP and ignoring gvim .swp files

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

When developing modules, I am being pestered by phantom make rules for gvim .swp files for things I have been editing.

I know that the file MANIFEST.SKIP can be used to selectively ignore files - I have created one that contains the regular expression

\.swp$
[download]

This now works correctly for make skipcheck, but I am still getting the problem when I build. Rerunning perl Makefile.PL does sort it out, but is still including rules for a .swp if one exists when it is run.

Thanks in advance

--

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)

Comment on MANIFEST.SKIP and ignoring gvim .swp files Download Code

Replies are listed 'Best First'.
Re: MANIFEST.SKIP and ignoring gvim .swp files by xdg (Monsignor) on Jul 29, 2005 at 11:11 UTC
This is a workaround answer rather than a direct one, but I've taken to storing all my vim backups/swap files in a single designated directory rather than scattered around. (I want them to exist, but I don't want them cluttering up my working space.) Put this in your .vimrc file (and create whatever directories you specify): `set backupdir=~/.vimbackups// set directory=~/.vimswap//` [download] The double backslash makes vim convert the full pathname of your file into the name of the swap/backup files created. Read ":h dir" and ":h bdir" for details. -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply] [d/l]
Re: MANIFEST.SKIP and ignoring gvim .swp files (vi) by tye (Sage) on Jul 29, 2005 at 13:57 UTC
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	[reply]
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)	[reply]