James Wilson wrote:
> Dave...
>
> On Jan 23, 2008 4:19 AM, Dave Lawrence <dlawrence_at_ad-holdings.co.uk> wrote:
>> You should be aware that a Cygwin build of svn.exe is NOT the same as a
>> "normal" windows build. Here are some of the differences:
>> * cygwin svn understands cygwin pathnames
>> * files with svn:eol-style=native will get LF endings on cygwin and CRLF
>> on windows
>> * checked out files will all be made "executable" by svn windows, on
>> cygwin only files with svn:exectuable will be executable
>>
>
> Thanks, I was unaware of those differences, but they all seem to make
> sense, except for the executable setting -- that kinda sucks and seems
> more like a bug than a feature.
Well I think Unix convention is that files aren't executable by default
so this behavior is kind of consistent with other programs. I think
files that are executable are automatically given this property when
added - except when added by Windows clients (otherwise everything would
have that property).
If for whatever reason you can see yourself adding files with TSVN but
at a later date checking them out in Cygwin (in a nightly build script
for instance) its useful to have an autoprop set to ensure .exe .bat
.dll etc get this property added (it can take ages to work out that the
reason your compiler doesn't work is because one of its dlls is non
executable).
>
>> PS I tried to compile svn 1.5 for cygwin the other day and to cut a long
>> story short it doesn't build (mainly the fault of the current version of
>> sqlite not building for cygwin)
>
> I had decided seriously not to try to compile specifically for time
> considerations. Very interesting though... also didn't know svn
> depends on sqlite.
Apparently its used by the new merge-tracking feature.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-24 17:54:09 CET