Understanding svn:eol-style interactions with other properties

I am trying to adapt a legacy system written in C to use SVN for version control.

This legacy system has components that are built and run on linux and also other components that are built and run on MS-DOS (yes, MS-DOS, although eventually it's going away!). Development will, for the most part, take place on Windows platforms. Builds will take place on linux and DOS systems. The build process for the DOS components is able to account for unix line feeds and react appropriately. However, there are a few directories whose files must retain their DOS CRLFs. So my thought is to go svn propset svn:eol-style=native globally and svn propset svn:eol-style=CRLF for those exceptions.

So far so good, but now we come to my main question.

There are also directories containing some unusual kinds of non-source stuff including DOS executables and libraries. When these are brought under SVN, SVN correctly guesses their svn:mime-type (at least most of the time) as application/octet-stream and also adds an svn:executable property. It seems that the presence of either or both (which?) of these properties prevents the global assignment of svn:eol-style which would otherwise have been applied to these files by the propset operation described above. Is this the case and are there any other interactions between svn:eol-style and other properties that I need to know about. Is there detailed information about the functioning of svn propset in these cases? The svn manual does not descend to this level of detail.

Thanks.
Received on 2010-09-03 16:46:55 CEST