On Tue Jun 03 12:56:44 2008, coke wrote: > > (That said, didn't we already solve the svk issue elsewhere? If so, no > harm in piggy-backing on that.) >
After my first post this morning, I got to thinking the same thing. So when I got home I grepped the repository for /svk/i, and came up with this: [li11-226:parrot] 505 $ fns . | xargs grep -in svk ./tools/util/templates.json:11:Parrot, or help develop Parrot itself, we recommend using Subversion or SVK on ./tools/util/templates.json:34:href=\"@[EMAIL PROTECTED]">Subversion</a> or <a href=\"@[EMAIL PROTECTED]">SVK</a> on ./tools/util/release.json:24: "svk.root" : "http://svk.bestpractical.com/"; ./tools/dev/mk_manifest_and_skip.pl:34:Recreates MANIFEST and MANIFEST.SKIP from the svn/svk directories. ./tools/dev/mk_manifest_and_skip.pl:35:So far tested with svn 1.2.0, svn 1.4.2, and svk 1.08. ./lib/Parrot/Manifest.pm:18: cmd => -d '.svn' ? 'svn' : 'svk', ./t/distro/file_metadata.t:35:my $cmd = -d '.svn' ? 'svn' : 'svk'; ./t/distro/file_metadata.t:276: elsif ( !( (-d '.svn' && `svn info .`) or `svk info .` ) ) { ./t/distro/file_metadata.t:284:# at a time. (do this to speed up execution for the svn/svk commands) ./t/codingstd/gmt_utc.t:46: # trim out svn and svk Id lines In r28055, I removed those references which either appeared in comments or were found in the .json files. That leaves lib/Parrot/Manifest.pm and t/distro/file_metadata.t -- which I will take a look at (though perhaps others should glance at as well). I think it's a safe assumption that if there are no references to 'svk' in our code base, svk can't pose any problems for us. (Correct?) kid51
