Re: Subversion's best-practice

Fabien.Bouleau_at_ses-engineering.com wrote:
> [...]
> 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.

It's exactly the way we go with my group: (so it's sound good to me)

third-party wich are deployed through source are integrated (source
only) using the
'vendor-branch' concept on our main repository (if needed), any binary
deployment
(of the third party, but also some local libs, with a low release
frequency) are hosted
on (currently) one alternat. repo (staging area);
a set of "svn:external" (from the main repo) help us to co a working
build tree.

like this, the depot of binaries can be splitted, hosted on separate
machine, etc,
without disturbing (so much) the main area.

regards

florian

-- 
--------------------------------------------------------------------
Seydoux Florian
http://www.spinx-technologies.com
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org