My only real complaint is the CVS "integration". I use the term loosely because, on Windows at least, getting cvs to work requires putty, pscp, pageant and puttygen. You must set up password-less connections by setting up public and private keys, then copying your public key to the remote CVS server. The whole thing is a pain. Anyway, it ought to work in theory but in practice, as any SourceForge user knows, you can't login to the cvs server (without getting kicked immediately anyway), nor can you copy the public key over. Thus, you can't get at your checked in files on SourceForge. Someone please correct me if I'm wrong.
I would rather they did what (I think) Eclipse does - store your password internally and send it to the CVS server as needed.
Oh, and the startup time could be significantly improved. But other than *that*, very slick application.
Getting keys to sourceforge (Score:3, Interesting)
Reply to This
Re:Getting keys to sourceforge (Score:2)
In any case I still prefer the approach used by Eclipse.
Alternate SourceForge SSH Keys (Score:3, Interesting)
The logged-in user page has a link to manage SSH keys. You just have to copy and paste them into a web form and wait six hours for all of the servers to synchronize.
Reply to This
Solaris support (Score:1)
Re:Solaris support (Score:2)
As for Solaris 2.5, we have a few machines around, but nothing anyone uses as a desktop. Personally, I think it ought to be purged from the company.