James Wilson wrote:
> On Jan 22, 2008 1:01 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>> The 'svn.exe' and 'svnadmin.exe' in our nightly build folders are there
>> in case you find a bug in TSVN and want to reproduce it with the
>> official svn client (if it happens there too, then the bug is in the svn
>> library and I have it easier to find the reason or come up with a
>> reproduction recipe for the svn guys).
>
> gotcha, guess that could be useful for people that don't already have
> an svn cli client installed.
>
>> If you want to 'upgrade' your existing svn client, then you have to
>> adjust the PATH env variable to not point to the original svn client
>> folder anymore but the TSVN bin folder where you copied the svn.exe to.
>>
>> But I would not recommend that. Just use your original svn client.
>
> My original client is the svn provided by cygwin, for which version
> 1.5 hasn't been released yet. So I had to download and setup separate
> binaries by hand. I'll just document here for posterity what I already
> did.
>
> Download svn 1.5 binaries for windows from
> http://merge-tracking.open.collab.net/files/documents/147/350/svn.win32.bin.httpd.r27562.zip
>
> Unzip to c:\cygwin\usr\local which will appropriately put the 1.5
> binaries in the /usr/local/bin folder.
>
> I figured that this would be enough...
>
> $which svn
> /usr/local/bin/svn
>
> $/usr/local/bin/svn.exe --version
> svn, version 1.5.0 (dev build)
> compiled Nov 1 2007, 17:54:29
>
> But for some reason it didn't work completely. Even though
> /usr/local/bin has precedence over /bin in my $PATH variable, it still
> seemed to be grabbing the old version installed in /bin. Very odd.
>
> $svn --version
> svn, version 1.4.5 (r25188)
> compiled Sep 19 2007, 23:10:31
>
>
> Had to backup current svn binaries:
>
> $ cd /bin
> $ mkdir svn-1.4
> $ mv svn*.exe svn-1.4/
>
> Link /bin/svn.exe to new 1.5 binaries:
> $ ln -s /usr/local/bin/svn.exe
>
> Check version:
> $which svn
> /usr/local/bin/svn
>
> $svn --version
> svn, version 1.5.0 (dev build)
> compiled Nov 1 2007, 17:54:29
You should be aware that a Cygwin build of svn.exe is NOT the same as a
"normal" windows build. Here are some of the differences:
* cygwin svn understands cygwin pathnames
* files with svn:eol-style=native will get LF endings on cygwin and CRLF
on windows
* checked out files will all be made "executable" by svn windows, on
cygwin only files with svn:exectuable will be executable
PS I tried to compile svn 1.5 for cygwin the other day and to cut a long
story short it doesn't build (mainly the fault of the current version of
sqlite not building for cygwin)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-23 10:20:26 CET