[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Managing only a few files in a directory tree?
From: |
Todd Denniston |
Subject: |
Re: Managing only a few files in a directory tree? |
Date: |
Mon, 09 Feb 2009 12:14:12 -0500 |
User-agent: |
Thunderbird 2.0.0.19 (X11/20081209) |
pmts wrote, On 02/08/2009 10:01 PM:
Hi, folks --
Ok, I'm old: I used RCS in the *80s*. :-)
I manage a suite of commercial, compiled apps in a handful of directories
in a directory tree, and each directory has one or two config files that
drive the behavior of the binaries therein. Doing a "cvs import" seems to
import *all* files in a directory, including the binaries that really don't
benefit from being managed in CVS. Throwing in a ton of -I's to ignore
certain files is a possibility, if somewhat ungraceful.
What's the best way to set up a CVS module or project which holds only the
couple of config files in each directory in the tree? What I've used works,
but is, shall we say, unpleasant. :-)
Thanks!
Don
1) understand, that unlike RCS, when you put files from a directory under VC
that directory is not now under control, i.e, importing your current structure
will not make the directory imported into a CVS 'sandbox'.
2) considering 1, the easiest thing to do would be:
copy the directory structure with config files and import it, then do a
checkout and populate the checkout with the appropriate binary files.
3) alternative to 2 is to create a repository directory,
check it out to a sandbox,
move the operational directory(ies) into the sandbox,
`cvs add` each directory and config file into the repository.
3 is probably what I would do, but I am strange.
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter