[Top][All Lists]

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

Ignoring files known to CVS, when updating

From: Marc-André Boucher
Subject: Ignoring files known to CVS, when updating
Date: Tue, 08 May 2007 15:14:59 -0400
User-agent: Thunderbird (Windows/20070221)

Is there a way to ignore files that are already known to CVS? The problem is I
want to deploy my project to multiple servers/environments/sites, but I don't
want to override the configuration files every time I create my deployment
I have a single directory with my project which I update using CVS, and
multiple directories with the configuration files of each of the
servers/environments/sites where I deploy.

I would like to run a single "cvs update" command to keep the project
up-to-date, but ignoring the config files so that I don't have to modify them
everytime they are committed in CVS.

I have modified them directly on the deployment server, and they merge
everytime I update the project, which is ok, but if the configuration files
are committed for some changes, I don't want them to merge : I'm gonna modify
them manually if I have to.

I know it seems like a software deployment problem, but the CVS part
is the heart of it. I have found other ways to do this, but they're too much
of a "patch" than a real solution!

Thanks again for your time. If there's a way to do this, that would spare me
some problems!

reply via email to

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