>>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.
This problem cannot be solved the the build-system;
and the problem is also not limited to build related problems
-> see my previous posting for detailed arguments.
> In the same situation, every version control system that I
> know of (and that does directory versioning) will behave analogously to
> Subversion.
Maybe (I only know cvs and svn).
But this does not solve the problem ;-)
Btw, subversion is better than other version control
systems in many respects! So it would be cool it
is better in this case, too! ;-)
In our case (replacement(!) of a directory containing temporary
files, where svn update fails without changing the wc)
the only solution I know is to delete the complete directory
(including .svn directories @%§&@) before update,
or to selectively delete all svn:ignore files before update
(how should I do this under windows? @%§$"%@)
Does anyone knows an alternative?
I think it would be cool to avoid such hacks,
especially since the user didn't do anything wrong.
Cheers,
Folker
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 19 23:16:53 2003