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

Re: Compiling against the repository

From: Ron Wilson <ronw.mrmx_at_gmail.com>
Date: Mon, 21 Apr 2008 11:07:34 -0400

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
Received on 2008-04-22 09:07:43 CEST

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

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