Re: setting the executable bit

Andy,

I missed the start of this thread due to e-mail problems at my end, so I
have no idea of the context.

> We use Linux and Windows development systems and the 
> developers decided they preferred to use TortoiseCVS as their 
> CVSNT client. Unfortunately the Linux executable attribute 
> does not exists on Windows so is never set when checked in 
> (Windows uses extensions like .exe to identify executable 
> behaviour). Thus when checked out to a Linux platform no 
> execute bit (these files will then need to have their execute 
> bit set every time they are checked out).

Yes and no.  CVSNT does try and store the executable bit, but its
success depends on many factors in including the file system (ntfs works
better than fat), whether you have cygwin installed (could be better or
worse), and the editing software that you use on windows (if it removes
the attributes).  The ntsec and ntea settings control CVSNTs behaviour
(just google cvsnt ntsec ntea).

This does not really seem to be a discussion about TortoiseCVS so maybe
it should move to the CVSNT newsgroup.

A commit option on CVSNT (or a server option) to ignore client side mode
attributes would be a good feature to add I think.  Eg: ignore client
side mode attributes from windows clients (use previous attributes or
use default attributes) and a way to define default attributes like
cvswrappers defines default substitution mode.

Regards,


Arthur


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H