Installing SVK 2.0 from source on Strawberry Perl Alpha 2
These instructions show how to build SVK from source using Strawberry Perl for Win32.
- Download Subversion binaries from http://subversion.tigris.org/downloads/svn-win32-1.4.2.zip
- Unzip Subversion binaries and install into a directory of your choice somewhere. Add that directory to your PATH environment variable. (I used c:\bin since I keep lots of command line tools there.)
- Download Subversion Perl bindings from http://subversion.tigris.org/downloads/svn-win32-1.4.2_pl.zip
- Unzip Subversion Perl bindings. Copy perl\site from the Perl bindings into Strawberry Perl's site directory (C:\strawberry-perl\perl\site) -- say "yes" to prompts about having folders already there.
- Set the LANG environment variable as appropriate (e.g. 'en_US.utf8')
- Without this, many "unintialized value" warnings are issued as SVK tries to identify a locale
- NOTE: Installing Win32::Console will cure this problem. --klight
- Open a Windows command shell and launch CPAN shell from the command prompt
- "install SVK" -- just hit return for the defaults on all the auto-install prompts
- SVN::Mirror will seem to hang on some tests -- just be patient and wait it out (go get a cup of your favorite beverage)
- Test svk (e.g. "svk help")
- "dmake test" should complete with 100% passing. There is some strange output for t/23commit-inter-nav and t/71autovivify but the tests pass.
- [For CPAN newbies (like myself): I was getting a lot of tests failures, but they were due to the test repos being created in a path with spaces. I changed C:\strawberry-perl\perl\lib\CPAN\Config.pm so every path in Temp point to a root dir (ie, c:\cpan\build, c:\cpan\sources, ...) and making sure %TEMP% doesn't contain any blank neither. It works fine now!! --Jorge]
- I've seen t/74view-mirror.t fail in some cases; diagnostics seem to include errors that say "Access Denied". Turning off real-time virus scanning seemed to prevent these errors. --Dagolden
- Configure your default depot (e.g. "svk depotmap -i")
- You may also want to make sure the your EDITOR environment variable is set appropriately to your preferred text editor. Be sure not to use spaces in the pathname.