Feature request: Read only checkouts

Hi,

I've just again read the thread "Repository files appearing in repository?",
in which some people expressed their need for a new feature in SVN. This
feature would be very close to the CVS option 'make checked-out files read
only' (-r).

Please note, that this is different from locking. This option would allow SVN
to much better integrate with our main development environment (LabVIEW), as
well as some others. These environments use the read-only flag as a method of
determining if this file was altered. In addition, LabVIEW will alter
contents of read-write source files occasionally (due to holding compiled
code and such in the same binary file, ugh!), but can be told to keep away
from read-only files.

As I understand, CodeWarrior also uses the read-only flag to signal
'unchangedness' of a file. Some CAD system do, too.

So what I need is this behaviour:
Whenever the SVN WC-lib checks or updates a file's status (no matter if 'co',
'up', 'status', 'log'...) it should set the file to read-only if it's
up-to-date AND unchanged locally. Ideally this behaviour could be controlled
via a property (can properties be set from a post-commit hook?), so that only
some files will be treated that way.

In the other thread, Erik Huelsmann asked:

- In what respect does CodeWarrior (or your tool) treat read-only files
differently than read-write files?

It will simply not change them on it's own nor let the user change the file.
User needs to manually 'unlock' (NOTE: LabVIEW unlock, not SVN) the file.

- When should files be set read-write, when read-only?

They should be set to read-only if they are up-to-date AND unmodified, and
NEVER to read-write. (This is taken care of by the tool).

- When is it ok to overwrite a read-only file?

Always, but it usually will be modified.

- If a file is copied, does it retain it's attributes?

Yes.

- Does that include read-onlyness?

Yes.

- How do directories fall into this picture?

They are handled fine as is.

I think that this feature would be useful to many people, perhaps with
slightly different behaviour. Comments?

Thanks for this great tool,
 Joerg

-- 
Leading SW developer  - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org