You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Yanghui Bian <yb...@vitesse.com> on 2003/04/17 19:06:21 UTC
RE: Thoughts on user issues and how to attract the CVS user base...
I have just tried Subversion version 0.21.0 (r5639).
For project westlake, the following external modules are set as the
property.
$ 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
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?
RD,
-----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
base...
"Yanghui Bian" <yb...@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
directory.
> 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
milestone.
However, I don't know if the bugs you encountered are these known
bugs, or are new unknown ones.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Thoughts on user issues and how to attract the CVS user base...
Posted by Ben Collins-Sussman <su...@collab.net>.
"Yanghui Bian" <yb...@vitesse.com> writes:
> 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.
It is a known bug that svn:externals do not work with 'svn status' or
'svn commit'. It's an unfinished feature at the moment.
> 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?
If you make a tag or branch, the newly copied directory will still
have the same svn:externals property, so it will continue to check out
the exact same externals.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Thoughts on user issues and how to attract the CVS user base...
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
"Yanghui Bian" <yb...@vitesse.com> writes:
> 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
> bla".
Yup, this is a known issue:
http://subversion.tigris.org/issues/show_bug.cgi?id=959
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org