Re: Proposal: svn:temporary property

Folker Schamel wrote:

>>> User B works on the same project but on different modules.
>>> User B is even not aware of the existance of fancy_module/subdir.
>>> But user B indirectly compiles fancy_module/subdir by executing
>>> a project make, creating temporary files in fancy_module/subdir.
>>> But now when user B does his regulary update,
>>> he will suddenly get an error about modified files in
>>> fancy_module/subdir, a directory, he has never heared about.
>>
>>
>>
>> Right. And "svn status" will tell him that that directory is no longer
>> under version control. Whereupon he will delete it, update again, and
>> the problem will go away.
>
>
> I think the philosophy of subversion should be that
> if user A and user B work on disjunct project parts,
> they should not interfer with each other,
> i.e. user B is not bothered by changes of user A or vice versa.
> svn:temporary would archive this.

No. What you've been describing is a consequence of a feature of the
build system. In the same situation, every version control system that I
know of (and that does directory versioning) will behave analogously to
Subversion.

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org