Everyone must actively choose (on demand) to update their working copy to reflect the latest state in the repository. The latest updates aren't automatically merged. That is because
a) they may not be ready to merge someone else's updates
b) merging updates may require manual intervention (it can't always be done automatically)
c) when should the updates be done - should something constantly be polling the repository to check for updates?
FYI - there is a tool available somewhere called the Commit Watcher or Commit Monitor.
That would allow an interested developer to be notified whenever someone commits a change to the repository.
Then they can choose to do an update from the repository.
Chuck
> -----Original Message-----
> From: Ian S. Worthington [mailto:IanWorthington_at_usa.net]
> Sent: Monday, April 21, 2008 8:04 PM
> To: users_at_tortoisesvn.tigris.org; ronw.mrmx_at_gmail.com
> Subject: Re: Compiling against the repository
>
> Thanks Ron.
>
> Maybe I've missed a concept somewhere? My understanding is this:
>
> In the repository I have several hundred include files. I
> can't compile directly against the repository but need to
> maintain some kind of external copy the compiler can find its
> includes in. The question is, after a developer takes a
> private copy, makes some changes, then commits them back to
> the repository, how does that external copy (not other
> developers private copies) get updated to keep in sync with
> the repository?
>
> i
>
> Ron Wilson wrote:
> > On Mon, Apr 21, 2008 at 9:50 AM, Ian S. Worthington
> > <ianworthington_at_usa.net> wrote:
> >
> >> How do I set up tsvn so that when I do a build of a checked-out
> >> component I have access to all the other header files I
> need in the repository?
> >>
> >> Or am I expected to maintain an exported version of the
> repository
> >> for this purpose and, if so, is there some way tsvn can
> keep that up
> >> to date for me when headers are updated?
> >>
> >
> > Are you talking about doing a build in a seperate working copy from
> > the one you are editing? If so, you can use a server side
> Commit Hook
> > to auto-update your build area.
> >
> > All the developers I work with edit and build in the same working
> > copy, using Update to bring in updated sources when ready, then
> > committing changes when ready. It would not make sense to
> automaticaly
> > update a developer's working copy, though it could be automated by
> > your build system. The reason tis does not make sense is that when
> > making a fix or other change, you generally need the rest of source
> > local copy to be stable. One the change is done, you update your
> > working copy, resolve any conflict and/or other problems,
> then commit
> > your changes.
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
> > For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
> >
> >
> > .
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-04-22 07:08:50 CEST