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

RE: revision numbers, and a single repo versus multiple repos?

From: Robert P. J. Day <rpjday_at_mindspring.com>
Date: 2004-12-20 21:22:10 CET

On Mon, 20 Dec 2004, Dale Worley wrote:

> From: Robert P. J. Day [mailto:rpjday@mindspring.com]
> > i want to break it into more than one svn repository (but with
> > each repo representing what you would call several CVS "modules").
> > one of the reasons is that, as i read it, revision numbers are
> > incremented on a per-repo basis.
> Our experience is that unless the projects are *entirely*
> independent, it quickly becomes a nuisance to work with more than
> one repository because no Subversion operation can manipulate more
> than one repository.

yes, i figured that out quickly enough. but i still might be able to
make this work since i want to create an entire build infrastructure
(using make or scons, perhaps), where my current project (i've gotten
kind of nervous using that word now :-) involves pulling together a
bunch of different software components to create an entire embedded

imagine that this embedded system will be built from two types of
software components: open source stuff (perhaps i'll keep all that in
one svn repo, tracking 3rd party sources), and proprietary, internal
bits (perfect for another repo).

now, if i have your typical recursive make structure, at each level,
the makefile will simply be responsible for knowing which software bit
to pull out of which repo. in that sense, it's not like those repos
have to communicate with each other -- they're really independent, and
it's just the make structure which has to access them, a bit at a
time, to checkout the appropriate component.

so it's not like i'd have a separate repo for *every* different bit of
software. but i might have a separate repo for each related
*collection* of software bits. and it should be obvious that those
two repos would never want to communicate with each other, since they
store wholly different kinds of data. it's only the make structure
that would access them.

anyway, i still haven't hit the sections on svn:externals or managing
vendor branches -- i suspect i'll get lots of info when i get there.


p.s. if anyone's done just this sort of thing -- used svn as part of
a build infrastructure to build an entire embedded system -- by all
means, i'd love to hear from you.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 20 21:25:24 2004

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.