I've been trying to use vss2svn to migrate our VSS repository to SVN.
However, our repository has over 1000 top level labels (of $\) which are
added by our automated build process. As indicated in the thread about
"Label support", you are aware that this leads to over 2000 levels of
nesting of the labels folder. E.g.
Labels
...
-build.1000
-labels
...
-build.999
-labels
...
-build.998
... (2000 levels of nesting)
The obvious solution to this is to (optionally) place the repository in
a subfolder. E.g.
labels
-build.1
Trunk-contents
...
-build.1000
trunk-contents
trunk
trunk-contents
Where $\ maps to trunk\.
I've had a look at the scripts in the hope of making the modification
myself (and of course passing it back), but I'm not really familiar
enough with perl or the vss2svn scripts to work out what needs changing.
Could you either give me an outline of what I need to change, or take
this as an enhancement request?
(I imagine there are various stages at which the "trunk" bit could be
inserted, but someone else probably has a feeling for the best stage to
add it. Would it work to do a simple minded thing in the Node module,
adding "trunk" to the start of the paths if and only if they don't begin
with "labels"?)
Thanks,
Tom
**********************************************************************
IMPORTANT NOTICE.
Confidentiality: This e-mail and its attachments are intended for the above
named only and may be confidential. If they have come to you in error you must
take no action based on them, nor must you copy or show them to anyone; please
reply to this e-mail and highlight the error.
Security Warning: Please note that this e-mail has been created in the
knowledge that Internet e-mail is not a 100% secure communications medium.
We advise that you understand and observe this lack of security when e-mailing
us.
Viruses: Although we have taken steps to ensure that this e-mail and
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure they are actually virus free.
Monitoring and Scanning: Cambridge Cognition has monitoring and scanning
systems in place in relation to emails sent and received to: monitor / record
business communications; prevent and detect crime; investigate the use of the
Company's internal and external email system; and provide evidence of
compliance with business practices.
**********************************************************************
_______________________________________________
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
