[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WinCVS remote repository, please help before I...

From: Rob Helmer
Subject: Re: WinCVS remote repository, please help before I...
Date: Wed, 6 Mar 2002 19:24:52 -0800
User-agent: Mutt/1.2.5i

On Wed, Mar 06, 2002 at 04:14:19PM -0800, sharkfish wrote:
> I need to know how to tell WinCVS where to look for my files.
> Next, I need to get WinCVS to see my files properly.  They say 'nonCVS
> files' now.
> What is a module?  Is there a step by step instruction manual that is
> CLEAR?  I'm confused about the way I'm supposed to indicate my server
> to connect to...why can't I just use
> How can I get WinCVS to see my files properly?


It sounds like what you need to do is set up a CVS repository.

A repository holds modules, modules are essentially a directory ( aka
folder ) inside a CVS repository.

The files that are kept inside a module are special version control
files, you have to use CVS to get a particular version of a particular
file. If you have these version control files available to the internet
they will not be useful to anyone without CVS installed.

It sounds to me like you need to set up a CVS repository ( look
at if you don't have a Unix server available to you ).
There you can download the peice of CVS that acts as a server,
WinCVS will be your client. It doesn't matter if these two peices
are on the same machine or not.

Do you want to use CVS to keep your website under version control?
You can use as your server, but you will need
to have some method of releasing some version of the files under
version control.

This can be as simple as a script ( batch file, shell, perl, whatever )
that does something like :

cd \www
cvs export module

Where "\www" is where your webserver keeps it's content, and
"module" is the module you create in CVS.

You can make it alot more complex and useful, by assigning
release tags and automating releases and such, but you should
probably get the CVS repository running correctly before you
dive into all the other things you can do with version control
and release management.

Hope that helps,
Rob Helmer

reply via email to

[Prev in Thread] Current Thread [Next in Thread]