François Revol wrote:
I prefer svn+ssh myself but SourceForge doesn't support it, they tell you to use HTTPS URLs with their projects as a developer. :-/ I've been able to submit changes over unsecure HTTP back to SF, but it really irks me that they require HTTPS for secure commits. It's just my luck that the BeOS version wouldn't support it. :-(Speaking of issues with the BeOS port of SVN, it seems that it'slacking support for HTTPS (and probably SSH though I haven't tested it) possibly due to a lack of OpenSSL (in a modern version at least) on BeOS. Has there been any progress in getting OpenSSL in the repository?Many of us use svn+ssh: just fine from BeOS. At least in Zeta it works fine.The diffs for the last OpenSSL and OpenSSH to be ported to Zeta were released (or the source code maybe). I have them just in case.
Raymond -- Raymond C. Rodgers http://www.raymondrodgers.com/
