> > Checking in binary files into CVS or any repository control system is > > usually a broken thing. You want to either check in the stuff inside > > the tar ball seperately (if its going to change), or just copy it into > > the archive by updating CVSROOT/cvswrappers This comes back to the point of my first post - I'm looking for an *easy* to manage system to keep track of one directory of files that are updated once in a while. We're not working on a huge code base with multiple branches, etc. I suppose we can check in the files inside the .tar.gz separately but was hoping to avoid that since the contents of this binary are maintained by a different department. I'd really rather keep it intact as it is. Will SVN be better equipped to cope with large binaries? I don't understand why CVS chokes on a 1GB file when all it has to do is move it from one directory to another. I even gave this machine 3Gb of swap so it had 5Gb of total memory space available but it still dies when doing a cvs checkout.