[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Best practices question

From: Jacob Atzen <jacob_at_jacobatzen.dk>
Date: 2006-09-21 18:00:31 CEST

On Thu, Sep 21, 2006 at 08:46:30AM -0400, Jonathan Wallace wrote:
> Hello,
> I have a question concerning best practices. I have a set of files and
> folders that make up a software program, let us call it program A, in
> URL/trunk. The main "executable" is a microsoft .mdb file which must be
> treated as binary and should only be edited by one person at any time as
> merges are impossible[0] on binary files.

You can enforce this with the locking features of subversion. Even if
you don't people will not be able to commit stale versions of the binary
back to the repository.

> There is also a program B that shares a subset of the files in A
> including the main executable. For the subset of files and folders
> shared between A and B, I'd like to insure that there is only one copy
> of those files in the repository.
>
> My first thought was to make B a branch of A but then if someone
> accidentally commits the main executable in a checked out copy of B, then I
> now have two copies. Obviously, one can merge this B executable back into
> the main trunk but this doesn't solve the underlying problem. I appreciate
> any and all suggestions.

Have you considered externals for the shared parts?

It might be easier to give better advice if you supply more details
about the directory layout of A and B.

-- 
Cheers,
- Jacob Atzen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 21 18:01:23 2006

This is an archived mail posted to the Subversion Users mailing list.