On Tue, Apr 02, 2002 at 12:06:59PM -0800, Imraan wrote: > Hi, > > I'm little confused. I understand that you are not to access the > repository directly and you are suppose to checkout to your local > computer. However, suppose we complete a project and want to transfer > the code to say a remote IIS server, from where do you transfer the > file? The repository files have been modified by rcs to have v > extension so they are not directly usable. So does that mean we must > checkout the latest revisions to our local computers and then transfer > them to our production servers remotely? >
Hi Imraan, In a nutshell, yes. RCS files are the revision history for your project; they belong on the CVS server, in backups, etc. *Never* on your webserver. It sounds like you need some kind of "build&release" process, for software anyway there is generally versions control, a build system, and some kind of packaging/distribution system. If you don't really need a "build" process, you can use CVS to help you with the "release" part.. just do a "cvs export" of the module, make an archive of it and install it on your remote webserver. In many projects I've worked on, we've made an automated release/distribution mechanism to update multiple servers, or just to maintain quality control and reproducable install processes. HTH, Rob Helmer _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
