On Wednesday 18 May 2005 07:52, Leopold Toetsch wrote:
I'd say we just drop this test. Whenever you do reasoanble work in the working tree, you got test files, editor swap file and whatnot.
Still it is one of the most often failing tests, because people tend to
forget to update MANIFEST when adding files to CVS.
It depends of course on how people organize their work. But I think there are basically two cases:
- manicheck a clean repo
- manicheck a working copy, where you compile and run tests
I have both parrot trees, usual work is: a) "svn up" in the clean tree b) rsync -au trunk/ leo c) work and compile in my tree d) manidiff && copy changed files back to trunk e) svn ci
Step d) and e) include some scripts that run a manickeck in the clean tree. But this sequence doesn't prevent from just forgetting to add a file to MANIFEST in leo/ :)
Garret Goebel wrote a commitinfo file which warned a commiter if he/she forgot to update the MANIFEST.
perl tools/dev/manicheck.pl in the clean tree does it
I have an updated version of t/src/manifest.t I was about to commit but is now conflicting with this latest version.
What about:
skip("number 6", 1) if -e parrot$EXE;leo
