Treating several related files as "one atomic thing"

[bryce_nesbitt]

I've got a set of 6 files I need to manage.  Several of these files
are indexes into other files.  They only make sense as a group.  Is
there a way to force CVS to treat them as a group?


It will never make sense to check in the files one-by-one.
It will never make sense to check out the files one-by-one.
It will never make sense to diff the files one-by-one
(in fact, only a special purpose diff utility can handle the files).
It will never make sense for individual files to have their
own version numbers.


I'd like CVS to enforce treating these six files as one atomic object,
with a single revision history.

Any suggestions?  Is this something other source control systems can do?

                   -Bryce


(I know that I can "cvs commit -f" the files to keep the same
revision numbers.  I know I can create a tag to bind a group
of revisions together.  I'm looking for more.)