Unfortunately, as neither cvs nor rcs normally operate on stdin, the best
I can come up with is wrapper scripts for all the commands that
uncompress targets and cause the applications to operate on temp files.
Unfortunately that wouldn't work as well with CVS.
If you wanted to go all out you could write, say gzfs, as an extension to
the Linux kernel that stored all files on the mounted partition
compressed. That should make it transparent to just about everybody who
doesn't notice the extra CPU cycles. Then put your repository on the
gzfs file system. AFAIK, there may be a gzfs out there already.
Derek
--
Derek Price CVS Solutions Architect
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
I will not skateboard in the halls.
I will not skateboard in the halls.
I will not skateboard in the halls...
- Bart Simpson on chalkboard, _The Simpsons_
Patrick K Notz wrote:
> Hi,
>
> I've installed and am happily using CVS on my user account here at
> school. The problem is that we're allowed only a limited amount of
> storage so I have to refrain from using CVS in some situations
> (projects with images, binary files, etc.).
>
> So, my question is: Is it possible for CVS to keep all repository
> files in a compressed format? Ideally, the compression would be the
> final step in committing and the first in retrieving revisions so
> that, for example, diffs would operate on the actual file and not the
> compressed file.
>
> Moreover, it would be nice if there were a way to do this so that a
> user could write their own scripts to (un)process the RCS files rather
> than to build compression into CVS. That way a person could do things
> like, say, encrypt the RCS files to make an even more secure
> repository.
>
> Any thoughts on how to do this?
>
> Thanks ~ pat
>
> <[EMAIL PROTECTED]>
