| Even if we assume that it's impossible to upgrade OpenSSH on a given platform
| for some weird reason,
I appreciate your effort in this, but I strongly suggest that you
refrain from calling reasons why people can't install the latest
versions of supporting tools "weird".
I agree. For example, Fink on the Mac only has svn 1.1 (not that this
is a showstopper IMHO), and Debian testing is "stuck" with the latest
3.8 openssh.
| the problem is probably going to be fixed by SVN 1.4 and
| the new svn+ssl:// protocol. Meanwhile, unlucky people will have to live with
a
| slower "svn diff -rR1 -rR2" remote operation.
Or write a script gccdiff that, for now, invokes svn on the read-only
svn:// script. It will go away with SVN 1.4.
I think that "moving away" from svn+ssh should not mean disabling --
just making it the not-preferred way for connecting.
Also, I see how this cannot be an option for somebody, but the mirror
can be remote (e.g. NFS-mounted) if you are using svk. Still (unlike
with a rsync CVS repository), you could push changes to the main GCC
repository. I think that in the end I'll put the svk mirror somewhere
on a university server. Of course you lose the offline operation that
Giovanni likes so much :-) but it's just like CVS.
Paolo
