Sathish Vasudevaiah wrote:
>
> I want to setup the following CVS environment
> and I am hoping that some of you will point
> out the problems with such a setup or some
> better ideas.
>
> - I have a desktop (Win95) on which I would
> like to install a CVS server. *Finally*
> this is where all the version control should
> happen.
Win95 cannot act as a CVS server. If you really want this
install NT (or Linux). However you can use shared directories
to (mostly) emulate the behaviour (mind the locking problems don't
bite you though).
> (1) On the desktop install WinCVS and checkout
> modules and update the repository as
> locally mounted.
>
>
> (2) Connect the laptop to desktop CVS server,
> checkout some modules and disconnect the laptop.
OK
> Now when the laptop is on the "go", I would
> like to change the modules but
> **under CVS control**. For this purpose,
> I will bring the checked out modules to a
> local repository using WinCVS.
CVS doesn't work like that. You check your modules in when you
connect back into the LAN. I suspect it could be arranged to have multiple
repositories (with a program to fudge the 'Root' files), but it'd get very confusing
very fast (how would you keep the version numbers in sync, for example).
Tony
--
#define QUESTION ((bb) || !(bb)) - Shakespeare
[EMAIL PROTECTED]
