João Gustavo wrote:
I have a VSS project with a lot of files using the SHARE VSS concept.
I want to use vss2svn to migrate the project to Subversion, but I need
to know how vss2svn handles this issue. Could anyone help me? What do
you do with SHAREs?
As far as I am aware, VSS is the only source control system that uses
this "share" concept, and to migrate to another source control system
such as SVN, you must either refactor your code not to rely on having a
file shared into multiple places, or create some other synchronisation
mechanism (such as a batch file) to copy a changed file to the other
locations.
On a non-windows system you would be able to use symlinks for a similar
effect, but I believe SVN doesn't support these on Windows.
On the product I maintain, I am currently planning on moving all the
shared header files into a central "include" location that is shared
between all projects, and doing something similar for shared .cpp files.
The code restructuring necessary for this is low priority though - still
going to be stuck with VSS until I get some higher priority tasks out of
the way, having at least done several test conversions to prove it will
work. Open to other ideas for dealing with shared/linked files.
--
Stephen Lee <[EMAIL PROTECTED]>
Software Engineer, Vision Group - Pro-Measure Leader
Wilcox Associates Inc. (U.K.)
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
