On 2/14/07, lightbulb432 <veerukrishnan@hotmail.com> wrote:
>
> So it's only refused when a change happens to a file that you've changed? If
> somebody changes a different file in the repository (but that still has
> dependencies with the file you've changed), the code in the repository could
> still break, right, even though the commit is accepted?
>
> Any strategies for resolving such a case to ensure the repository contains a
> fully functioning code base, or is this a usual part of the development
> process?
>
> (e.g. Any way of declaring a dependency of one file on another so that you
> can't commit a file without first resolving conflicts not only in that file
> itself, but in files you've declared that it depends on. If not, any
> thoughts about this as a feature request?)
Subversion has no concept of inter-file dependencies. Sounds more like
the responsibility of a build system or development environment, not a
version control system.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 14 18:37:24 2007