[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
13 Aug 2001 17:08:32 +0200
Gnus/5.0807 (Gnus v5.8.7) Emacs/20.4
"Mark Lancisi" <address@hidden> writes:
> Does anyone know how cvs handles checkins of large binaries?
> I'm looking to checkin a 30Mb tarball. I've heard cvs might have problems
> with this..
> Thanks in advance for any help
See http://www.cvshome.org/docs/manual/cvs_2.html#SEC27 for some info
on the subject.
Note that it is the server side that could use some 300MB memory and
Depending on why you want to do it, there are two ways to avoid this:
If you are storing a distribution (the result of a build) you have
really passed the usefulness of CVS. The file will never ever change
again so put it somewhere safe (CD in a safe _and_ a central online
storage for easy access).
If it is something you need in your development process, either "cvs
import" it and keep track of changes on individual files or store it
somewhere, keeping just a reference to it in your cvs repository while
keeping your diffs in cvs (easily get hairy).
Or make sure you have 256 MB physical memory in your cvs server (or
workstation if running cvs in local mode) and 30MB files should be
less of a problem until you have changed it 20 times and the
rcs file is 600MB.
If it doesn't change you need not version control it.
If it does change often, why keep it in a tar ball?