If the requirement is to be able to commit large binary files regardless
of the method used to store them, then there may be a tweak to the CVS
configuration available. If the requirement really is to disable version
history, then you're out of luck for the moment.
With regard to the configuration tweak: The RCS build procedures sense
various capabilities of the underlying system, and changes its implementation
to use the most efficient mechanism possible. One of these optimizations
is to mmap an RCS file before modifying it on BSD-derived systems, essentially
pulling the entire RCS file into virtual memory.
This optimization was controlled by an #ifdef. If you switch it off,
then the RCS file will be updated through stdio and swap space is no longer
a factor.
I've done this in the past with real RCS-based versions of CVS. Now that
RCS has been reduced to a library, things may be different. But it's
worth a look if it will meet your needs.
--- Forwarded mail from [EMAIL PROTECTED]
I'm trying to figure out a way to have binary files in the repository
which do NOT story any revision history. One might ask what the point is
to this, as it's esentially the same as just copying the file directly.
My reason for needing this feature is that I have recently convinced my
company to try switching over to CVS (from Visual Sourcesafe) for a while,
and they are used to being able to store all files (including huge binary
audio files) within the repository by just turning off revision history on
large binaries. In particular, there are some 200MB files which actually
crash the server if you try to commit them, since it actually overruns the
real memory + swap.
--- End of forwarded message from [EMAIL PROTECTED]
