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

Re: Re: Build question

From: Hari Kodungallur <hkodungallur_at_gmail.com>
Date: 2005-11-07 13:08:52 CET

On 11/7/05, Robert Schneider <r.schneider@weingartner.com> wrote:
> > -----Original Message-----
> > From: Dimitri Papadopoulos-Orfanos [mailto:papadopo@shfj.cea.fr]
> > Sent: Monday, November 07, 2005 12:26 PM
> > To: users@subversion.tigris.org
> > Subject: Re: Build question
> >
> > Hi,
> >
> > > What do you do when a build process fetches the sources of several
> > > repositories? This is not an atomic operation, right?
> >
> > Could you give more details on this use case? I feel that if you have
> > different repositories, then you don't need atomic operations because
> > different repositories are loosely related. If you need different
> > projects to be closely synschronized, then maybe they should live in
> the
> > same repository.
> >
> For example, you could have a special text box control that is used in
> several projects. Would something be wrong when it is built with other
> (client-) applications? Is something wrong designed when I have to build
> from different repositories?
> I'm a newbie not an expert, so tell me please if I do something
> stupid...

I am not sure checkout operations are atomic. You do get all files at
a particular revision, but the checkout is not all or nothing. If some
error happens while checking out, it is aborted and you are left with
a partila working copy.
And if you are checking out from multiple repositories, it is quite
possible that you are not getting the snapshot from all repositories
at the very same time.

-Hari Kodungallur
SpikeSource Inc.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 7 13:12:12 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.