[p4] How to create RCS file errors

Ivey, William william_ivey at bmc.com
Tue Sep 25 13:56:30 PDT 2007


Got an odd error message a little while ago, something about the

RCS file not having an EOF.

 

This was our built image distribution server running on Windows.

(Our "real" server runs on AIX.) Images are added/edited/deleted

automatically a couple of times a day. It's that automatic add that

got us.

 

Well, a big part of our images now consist of self-extracting .bin files

for unix. Perforce had correctly identified these as executable text

files. What had not occurred to me was what that meant to the

size of the RCS files. Submitting 100-120 MB files of uuencoded

data tends to bloat the diffs something wonderful. Eventually, it

appears, the files become a little too big...

 

Just thought I'd toss this out for anyone else who might encounter

such errors. Changing the file type to binary+x fixed it right up. (And

you wouldn't believe how much faster the submits are now that it

isn't diffing all that junk.) Adding a line for .bin files in the
typemap

table should keep this from happening again (for a while).

 

-Wm

 



More information about the perforce-user mailing list