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.
Marcel Stör wrote:
> Right, so my initial description was correct after all.
You mean that C:\CVS is the root of your repository? Then you probably have
a sandbox somewhere.
>> The answer depends a bit on whether C:\CVS is the root of a sandbox
>> or of a repository. I think if it is a repository, you can leave it
>> where it is. If it is a sandbox, you just do a fresh checkout into a
>> different location.
>
> Now your previous post ("cvs chacl is to be used in a sandbox") is more
> comprehendable to me. So, the sequence would be checkout/cvs
> commands/checkin?
Not really. checkout and checkin /are/ cvs commands. If you are working
with the repository, you already have a local sandbox, so most likely you
don't have to checkout anything. Just cd into that sandbox and run the cvs
chacl command from there.
There's also the cvs rchacl command; this can be used without a local
sandbox. But I recommend to start with chacl and working in a local
sandbox. It is a bit more "graphic" IMO. (It also saves some typing in the
beginning, as you are likely to run several times the chacl and the lsacl
commands in the same directory. With chacl, you cd into that directory once
and then just issue the command repeatedly. With rchacl, you have to give
it the full path of the module each time.)
> Except for ACLs I've using all of this for quite some time. However,
> since I've only been using it through my IDE's CVS plugin (Eclipse) I
> never had an urgent need to understand in detail what's going on on the
> other end of my CVS connection.
Understanding the command line commands becomes crucial the moment you
leave such an environment for doing something more "advanced". I don't know
whether Eclipse has something that allows you to look at the commands it
sends to cvsnt and the resulting output. If it doesn't, maybe install
WinCvs and work a bit with it. It shows you every command as it gets sent
to cvsnt and the resulting output. This is quite useful in understanding
the common procedures.
Gerhard