bianyanghui@yeah.net writes:
> Hello, I am trying to transfer from CVS to subversion which acts as
> the next version of CVS. But I am in trouble with checkout and
> commit command which have different behavior from CVS. In CVS, If I
> run "cvs co module_name" when there is already a working copy of
> this module, cvs will not update the working copy except for the
> files not updated. But SVN re-checkout all the files except for the
> files modified locally. It causes the project to be recompiled as
> timestampe changed. It's not a big issue. I could just avoid it by
> running update.
Yes, svn is slightly different than cvs. 'checkout' is used to create
a working copy once. After that, you should run 'svn up'.
> In root directory of svn repository, I have libraries as lib1, lib2,
> lib3. They are shared modules for project. The project proj1 is in
> the root directory too. In working copy, I would like the libs under
> directory of proj1. But the trouble is that: If I run svn commit
> under proj1 directly, it only commit the changed file for
> proj1. Files modified but in lib1 and lib2 will not be commited. For
> CVS, it will examine the sub directory and commit the changes to the
> correspoinding module. The same problem for Status/update
> command. Any idea to work around it? Thanks
Yes, you want to use the svn:externals feature. You can read about it
in chapter 6 of the Subversion Book:
http://svnbook.red-bean.com/book.html#svn-ch-6-sect-3
At the moment, I don't think 'commit' or 'status' traverse externals
definitions, only 'update'. I can't remember. I think we may need to
file an issue on this.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 3 18:44:01 2003