>>Since your're checking out in windows
I'm not. I'm using Tortoise but both the repository and target are on the
unix side. I use the windows workstation for some file editing and general
management. Most stuff I do through a telnet connection to the unix box and
via Samba when I'm not worried about its missing links :)
Incidentally, I get fine results through the svn commandline, which does
confirm that svn is storing the links properly.
>>1. If you have a Unix box available, make it your Subversion server.
>>svnserve is hell lot faster on Unix, than on Windows. For repositories
that are used over the network it's ususally
>>better to use the svn: or
>>http: protocol rather than to access the repository directly via file:.
Yes, that's what I have. And I ordinarily use https (webdav) protocol. I've
established the svn server but don't use it.
2. Use TSVN for you Windows working copies
>> I don't put anything in the windows filesystem. No working copies at
all. This is what perplexed me a bit. Maybe Tortoise is temporarily
storing stuff on the windows filesystem which may be one reason why it has
trouble connecting between a unix repository and a unix target.
>>3. Use the native CLI or a native/JAVA GUI client for your Unix working
copies. You won't find a GUI client that's as
>>mighty, well-reasoned and stable as TSVN but you will find one that
satisfies your needs. If not, use scripts or write a
>>wrapper to manipulate your working copies. You can still use TSVN for
browsing, diffing etc.
That's what I am going to do. In the meantime, I'm just using the
>>You also might want to consider your using of symlinks. Maybe you can
substitute your symlinks by svn:externals. Or you
>>might want to accept some redundancies (and their disadvantages) for the
pleasure to use TSVN (as I did).
As I've looked at the project tree there are only a few isolated instances
where symlinks are part of the mix, and these are mostly for the final build
target output (an set of directories that are packaged into an image file
for a flash rom). However I was worried that there might be other unix file
attributes which were being lost when using Tortoise.
Since I've been pounding on this for a few days now it's clear that I *can*
use Tortoise for most of the tasks, but will have to use the commandline for
sections of the project that have links.
Great suggestions, Sven. I agree with your sentiment. Tortoise is well
done. I hope someday it can serve my particular case. I'm certain that I
am not alone.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Aug 10 02:08:22 2005