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

RE: Controlling 1 projects included in another

From: <andy.glew_at_amd.com>
Date: 2004-06-02 17:14:54 CEST

> Also take a look at 'externals', maybe that is a better way
> than to keep symlinks up-to-date.
> Uli

Externals seems to be the Subversion way.
At least, that's what I am doing
- although it results in great duplication
of code in the checked out workspace.

One thing: when you create a "tag" version
via svn cp, the externals reference is not copied
- it still points to the latest version
(or whatever version you specified)
of the library.

I.e. the externals does not get cp'ed or checkpointed.

If you want to make a true checkpoint of a module,
including whatever external modules it depends on,
you have to go and modify the externals.

Another way is to record, in a file, possibly generated
in build, the revisions of all files that a checkpoint
depends on, both in the current module and in the
externals. (For that matter, the paranoid among us record
compiler and shared library versions.) This file itself
can be checked in; with suitable tool support, it can also
be used to check out.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 2 17:16:47 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.