Thanks,
leo
> No need to parse the XML files, "svn list -R" lists everything in the repo.
>
> And I suppose I just volunteered myself for the job.
$ svn list -R
svn: '.' is not a working copy
Doesn't work when svk is used to check out the copy. But in that case
svk list -R does.
Nicholas Clark
No need to parse the XML files, "svn list -R" lists everything in the repo.
No XML parser? Bummer, it would be sooo much simpler. ;-)
C:\parrot\.svn>perl -MXML::Simple -MData::Dumper
-e"print(join \"\n\", keys %{XMLin('entries')->{entry}})"
encodings
ops
pf
ast
PBC_COMPAT
MANIFEST
...
VERSION
build_tools
README
Ron
Hmm. Maybe this should be a commit action and not a test.
It was under CVS. I'm pretty sure everyone ignored it there :)
-R
Well, it always depends, how responds looks like:
Committed revision 1234
*********************************
ATT MAINFEST ERROR
missing bla.bla ...
*********************************
> -R
leo
They wouldn't ignore it if it caused the commit to fail now would they.
This is very similar to what it did under CVS, although maybe not
quite as big.
Anyway, if this is something the community wants, if someone could
implement a first pass at the hook script, we can run it. It'll need
to use svnlook cat to look at the Manifest, svnlook changed to detect
new files or removed files, and then compare. Actual details are up
to the implementer.
Many thanks to Garrett Goebel who created our CVS implementation.
-R
That is a little harder to miss. :)
In CVS, it was just..
manicheck: Not in MANIFEST: $file
manicheck: No such file: $file
(Anyway, as said before - if someone writes the script - we'll run
it.)
-R