How does MacCVS Pro cope with checking in resource files?
CVS has its origins on UNIX, and thus knows nothing about the Macintosh system of having two forks per file, one for resources, and the other for data. We thus have to get it to treat files with resource forks as binary files, and somehow encode both forks in one stream for sending to the server. AppleSingle encoding is used for this, so files with resource forks get added with the -kb option, and sent to the server as AppleSingle data. MacCVS Pro, however, needs to store locally the encoding used for a file so that it can send the appropriate data during an update operation, and this data is stored in the ‘mcvs’ resource, in which there is a flag that states whether a file was checked in as AppleSingle or not. When checking out, MacCVS Pro ‘sniffs’ the data of binary files sent from the server, to determine whether to treat them as AppleSingle, and thus decode data and resource forks. It does this by checking for a valid AppleSingle header at the start of the data. Any file without th
Related Questions
- Does Transverter Pro do PostScript error checking? In other words, is it a good tool to preview files with questionable PostScript before sending them to another PostScript RIP?
- How to delete ALL files on hard drive, except ONE data folder so I can reinstall XP Pro?
- How does MacCVS Pro cope with checking in resource files?
