svn tree structure advise

Question

I have inherited a big project which isn't under any version control. The project is big: around: 9000 files & 600 directories, so We should keep the structure even if it isn't organized the svn way.

The structure is as follows:

-\Src
   -\Common
   -\Help
   -\Lib
   -\TheProject
     -main.pas
     -more-files.pas
     -\Engine.A
     -\Engine.B
     -\Engine.C
     -\Common
     -\Utils
   -\SomeMore
   -\SomeMore

For some customers we use Engine.A, for others Engine.B, etc... Before we do any progress we rename 'Engine.A' to 'Engine' --> develope --> compile -->rename back to Engine.A. Same for all other engines folders.

Any suggestion how to work that out? Please note: Each engine only change about 10% of the files, so branch will be a lot of work on.

Answer 1

Checkout the official svn book.

The chapters about branches and merging should be interesting and give some guidance.