I agree, perhaps we could not ship the cvs.exe executable at all as part of
NAnt, but just direct users to the #cvslib website.
Clayton, what do you think ?
Gert
- Original Message -
From: Simon Steele [EMAIL PROTECTED]
To: Nantdev [EMAIL PROTECTED]
Sent: Monday, March 22, 2004 5:43 PM
track
of versions (I deploy the .dll and .exe in one go), and the client does
not take up a lot of space.
Clayton
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: March 22, 2004 11:17 AM
To: Simon Steele; Nantdev
Subject: Re: [nant-dev] cvs.exe - bad naming
]
Sent: Monday, March 22, 2004 7:11 PM
Subject: RE: [nant-dev] cvs.exe - bad naming
Hi Gert and Simon,
I would prefer to just change the name of the sharpcvslib binary and
leave it in the NAnt repository as it means the basic cvs commands work
out of the box in a situation where there isn't
It is not a win32 only binary Scott, it is a command line client for
sharpcvslib which is pure c#.
Clayton
-Original Message-
From: Scott Hernandez [mailto:[EMAIL PROTECTED]
Sent: March 22, 2004 7:43 PM
To: Nantdev
Subject: Re: [nant-dev] cvs.exe - bad naming
Why do we need
, 2004 4:11 AM
Subject: RE: [nant-dev] cvs.exe - bad naming
Hi Gert and Simon,
I would prefer to just change the name of the sharpcvslib binary and
leave it in the NAnt repository as it means the basic cvs commands work
out of the box in a situation where there isn't a cvs binary installed
(i.e
PROTECTED]
Sent: Tuesday, March 23, 2004 4:11 AM
Subject: RE: [nant-dev] cvs.exe - bad naming
Hi Gert and Simon,
I would prefer to just change the name of the sharpcvslib
binary and leave it in the NAnt repository as it means the
basic cvs commands work out of the box in a situation where
