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

RE: Thoughts on user issues and how to attract the CVS user base...

From: Yanghui Bian <ybi_at_vitesse.com>
Date: 2003-04-17 21:06:21 CEST

I have just tried Subversion version 0.21.0 (r5639).

For project westlake, the following external modules are set as the
$ svn propget svn:externals
src/lib1 http://test/repos/lib1
src/lib2 http://test/repos/lib2

Both "svn update" and "svn checkout" work perfectly. SVN
updates/checkouts the external modules.
When I run "svn status", it only give the status of the root module.
$ svn status
M Makefile
? src/lib1
? src/lib2
It won't check status of the external modules. Writing a wrapper is not
so easy to fix it especially when you need to filter out the "? bla

A more complicated issue is about the TAG/Branch. If I make a tag on the
root module, What should SVN
do to the external modules?
Will it be difficult for Subversion to checkout the snap with both root
and external modules of the tagged revision?


-----Original Message-----
From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
Sent: Tuesday, March 25, 2003 1:32 AM
To: Yanghui Bian
Cc: Justin Erenkrantz; Tim Moloney; dev@subversion.tigris.org
Subject: Re: Thoughts on user issues and how to attract the CVS user

"Yanghui Bian" <ybi@vitesse.com> writes:
> For several projects with shared libraries, it seems that external
> module property is the only way to
> share cross-project libraries. Unfortunately SVN doesn't support
> recursively update/status external
> modules of the project when running the command from the root
> It's not so easy to write
> a command wrapper especially when you need to filter out the annoying
> warning from SVN command.

An example might help here. There are some known bugs related to the
svn:externals property; they are scheduled to be fixed before
Subversion 1.0, although they are not scheduled for an imminent

However, I don't know if the bugs you encountered are these known
bugs, or are new unknown ones.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 17 21:07:21 2003

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.