Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> Do any of you know if the WinCVS list of protocols is "hard coded" ?
It currently is. AFAICT Jerzy is already working on a more generic approach
though.
> Is there any way to get the current WinCVS (1.3.12.1 Beta 12) to connect
to
> cvsnt with the :sserver protocol?
You should be able to use WinCvs for working with existing sandboxes that
have been checked out with the new protocol. Once a sandbox has been checked
out the CVSROOT settings of WinCvs do not really matter anymore unless you
use the -d option (aka "force using current CVSROOT").
The only commands you will not be able to run from WinCvs are Checkout
(although this is probably only true for the very first "fresh" checkout),
Import and Login. If you run these from the command line to create your
modules and sandboxes you should be able to continue working in WinCvs. Note
that you will have to configure WinCvs to use the cvs.exe that supports
:sserver: . I don't think the one that came with WinCvs 1.3.12 already does.
Hope this helps.
Oliver
---- ------------------
JID: ogiesen at jabber.org
ICQ: 18777742
(http://wwp.icq.com/18777742)