Read the following chapter in the book (Advanced Topics: Externals
Definitions).
http://svnbook.red-bean.com/svnbook/ch07s03.html
Unless I miss my guess, the Subversion project itself uses this to
incorporate some or all of its external library requirements (apr, apr-util,
neon, etc.)
PS - it's "svn" not "sbv".
> -----Original Message-----
> From: Frank Munch [mailto:sm_sbv@u5.com]
> Sent: Wednesday, July 28, 2004 1:08 PM
> To: users@subversion.tigris.org
> Subject: How to set up projects with libraries
>
>
>
> Hi,
>
> is it normal that a developer runs sbv with more than one
> project at a
> time, due to the existence of libraries?
>
> I am new to setting up version control, so I'd hope someone
> might have a
> good idea here.
>
> Let's say I have two projects, A and B. They share a library,
> libAB and
> also a general library, libGeneral.
>
> So, if someone works on A he will also need to stay updated
> for libAB and
> libGeneral.
>
> Now, which of the the following statements are more true?
>
> A)
> It is perfectly natural and common to keep A, B, libAB and
> libGeneral as
> separate projects, so a developer working on A runs three
> commands to be
> fully updated
>
> sbv ... A
> sbv ... libAB
> sbv ... libGeneral
>
> B)
> No, that is not smart, there's a better way to do it...
>
> Thanks in advance for any answers/ideas.
>
> Best regards
>
> Frank Munch
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 28 19:15:02 2004