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

Subversion's best-practice

From: <Fabien.Bouleau_at_ses-engineering.com>
Date: Tue, 8 Jul 2008 12:16:25 +0200


I am currently facing a problem with Subversion's best usage with my
co-workers. We are working on various projects, i.e. we have more than 20
Subversion repositories. And of course we are using third-party APIs and

According to the documentation, there is the vendor branch development
scheme. I have some concern about putting the APIs and third-party tools as
such because:

 1. The third-party APIs and tools uploaded are binary.
 2. They are not intended to be modified but used off-the-shelf.
 3. Binaries make the repository grow like Hell
 4. Different projects (repositories) may use the same third-party APIs and
tools and duplication makes my teeth screech.

Therefore I had the following idea: to setup a "third-party" repostory
where we would drop the third-party binaries and sources as vendor branch
to keep track of the versions (using tags) and refer to it from the various
projects using svn:externals.

Does that sound correct to you? Any other suggestion?

Thanks & Best Regards,


This e-mail contains proprietary information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-08 19:38:17 CEST

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.