Perforce Public Knowledge Base - Moving Binary+D Files
Reset Search
 

 

Article

Moving Binary+D Files

« Go Back

Information

 
Problem

Move binary+D files between platforms that use different line endings, for example, from Windows to Linux.

Solution

When you move Perforce type binary+D files from Unix to Windows or from Windows to Unix, all of the line endings on the Perforce Server archive files must be converted to the native line end handling: LF on Unix and CRLF on Windows. In this respect, converting line endings on binary+D files are no different than converting other RCS format text files (*,v) in the Perforce Server archive.

The general process for converting Perforce archive files is detailed in

As demonstrated in the PERL example above, all carriage return and line feed combinations (\r\n) in the "*,v" archive files are converted to single line feeds (\n).

The same line end conversion can take place using other scripting tools and invocations; the important point is that all line endings in the binary+D archive file should be normalized to the platform native line ending convention.

Note: Perforce does not create binary+D type files by default. The existence of these type files is generally the result of a conversion from CVS, where binary files are stored in RCS text format (type binary+D, in Perforce). It is recommended that users converting from other version control systems change any converted binary+D type files to Perforce type 'binary' files immediately after their initial conversion to Perforce. Perforce type 'binary' files are stored on the Perforce Server as a whole revisions in separate files in gzip format.

 

Related Links

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255