Svn and module support

[William Uther <wi...@cs.cmu.edu>]

On 1/5/02 1:24 PM, "Nicklas Larsson" <ki...@lysator.liu.se> wrote:

> Now, when I read that 1.0 will probably not include annotate and module
> support, the most obvious question is, how much longer will it take to
> finish the version with annotate and module support?

svn already support "poor man's modules"?  It has `svn switch` :)

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.

% mkdir svntest
% cd svntest
% svnadmin create repos
% svn mkdir file:///Users/will/svntest/repos/trunk -m "add trunk dir"

Committed revision 1.
% svn co file:///Users/will/svntest/repos/trunk
Checked out revision 1.
% cd trunk
% svn mkdir myproj
% svn mkdir myotherproj
% svn mkdir mymodule
% cd myproj
% svn mkdir mymodule
% cd ../myotherproj
% svn mkdir mymodule
% cd ..
% svn commit -m "set up stuff"
Adding    mymodule
Adding    myotherproj
Adding    myotherproj/mymodule
Adding    myproj
Adding    myproj/mymodule

Committed revision 2.
% ls
mymodule     myotherproj  myproj
% cd myproj
% svn switch mymodule file:///Users/will/svntest/repos/trunk/mymodule
Updated to revision 2.
% cd ../myotherproj
% svn switch mymodule file:///Users/will/svntest/repos/trunk/mymodule
Updated to revision 2.
% cd ../mymodule
% cat > modulefile
this is the modulefile
% svn add modulefile
A          modulefile
% svn commit -m "add modulefile"
Adding    mymodule/modulefile
Transmitting file data .
Committed revision 3.
% cd ..
% svn up
A  ./myproj/mymodule/modulefile
A  ./myotherproj/mymodule/modulefile
Updated to revision 3.
% cd myproj/mymodule
% ls
Modulefile
% more modulefile
this is the modulefile

Later,

\x/ill          :-}


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Svn and module support

[Nicklas Larsson <ki...@lysator.liu.se>]

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

* 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
module.

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 <wi...@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

Re: Svn and module support

[Karl Fogel <kf...@newton.ch.collab.net>]

William Uther <wi...@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