Guys, I've just been reading up on cvs and have come across this in the sourceforge "use of cvs" faq to be found at
https://sourceforge.net/docman/display_doc.php?docid=768&group_id=1 The reason I bring this up is because lib/images/banner.ppm is a binary file. I presume that this "cvs admin -kb" stuff is relevant to it? Alternatively, of course, we could always store banner.ppm in ascii mode. Regards, Angus ------------------------------------------------------- Binary File Handling One of the weak spots within the design of CVS is in the handling of binary files. The diff mechanism that CVS relies on does not properly cope with binary files; it is necessary to add a special keyword flag on binary files to ensure their integrity within a repository. The use of this keyword flag (added through the use of the "cvs admin -kb filename" command) causes the CVS repository to keep a complete copy of each revision of that file, rather than diffs between revisions. Generally, binary files should only be stored in your repository if they have a direct bearing on your development work, and cannot easily be auto-generated from the source files; i.e. compiled binaries can generally be left out of your CVS repository, since they are regenerated each time the program is compiled. Care should be taken in deciding which binary files need to be stored within your repository; they can consume a significant amount of disk space. For binary file types, such as images, to be handled correctly within your repository when they are imported or added, you may add an entry to the cvswrappers file within the CVSROOT module for your repository. For cases where you need to enable the binary flag on existing files in the repository (i.e. if they have been added or imported without this flag being enabled by your cvswrappers file), this may be done using the "cvs admin -kb filename" command.
