[CMake] CTEST_CHECKOUT_COMMAND vs. CTEST_UPDATE_COMMAND

[Convey, Christian J CIV NUWC NWPT]

Thanks.  How does ctest know whether to employ "CVS_UPDATE_OPTIONS" vs. "SVN_UPDATE_OPTIONS" ? 

Also, the format you gave for "CVS_UPDATE_OPTIONS" looks like it has hte format of a line in the cache file.  Is there some reason I'd need to force it into the cache, or is it okay for me to achieve the same effect using a SET(CVS_UPDATE_OPTIONS ...) call?

- Christian

> -----Original Message-----
> From: Karthik Krishnan [mailto:karthik.krishnan at kitware.com] 
> Sent: Thursday, June 24, 2010 11:51
> To: Convey, Christian J CIV NUWC NWPT
> Cc: cmake at cmake.org
> Subject: Re: [CMake] CTEST_CHECKOUT_COMMAND vs. CTEST_UPDATE_COMMAND
> 
> You can specify the update options.. for instance : 
> 
>   CVS_UPDATE_OPTIONS:STRING=-d -A -P
> 
> similarly, there's
> 
>   SVN_UPDATE_OPTIONS

[snip]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5218 bytes
Desc: not available
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100624/14bb5207/attachment-0001.bin>