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

Re: Svn and module support

From: Nicklas Larsson <kilsmo_at_lysator.liu.se>
Date: 2002-05-01 23:22:07 CEST

The way that we are thinking of using the source control system is like

* We want to split up the code into modules. Each module will exist in a
number of versions.

* We are delivering on a number of platforms.

* We are delivering a number of products on each platform.

* Every product has needs of different sets of modules, and will need
different versions of each module.

* A product should be set up in the system so it can check out all the
modules with the right versions with a single command. When one person
working on this project has set up the modules that should be used in the
product, then all other members of the group can check out the product

I am not a CVS expert (and not a SubVersion expert either :-)), but from
what I understand, the working model above can be used together with CVS,
but you will need to use some special tricks to make it working.

So, will the described working model be:
1: Easier to follow with SubVersion
2: About the same difficulties as with CVS
3: Harder to follow with SubVersion (or almost impossible)

// Nicklas Larsson

On 1 May 2002, Karl Fogel wrote:

> William Uther <will+@cs.cmu.edu> writes:
> > svn already support "poor man's modules"? It has `svn switch` :)
> Today is my day to respond to module stuff :-). See the recent
> changes to
> http://subversion.tigris.org/issues/show_bug.cgi?id=517
> for module plan.
> > Obviously you'd want something better for full support, but what it has is
> > usable. You do have to set up the links to the module manually for each
> > working copy.
> The problem with using switch and svn cp for module support is that
> each copy becomes a branch -- the changes on the branch are no longer
> happening on the original line. Badness :-). I don't think useful
> module support can be had this way.
> -K

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 1 23:23:32 2002

This is an archived mail posted to the Subversion Dev mailing list.

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