While developing a PHP+JS web application we always try to separate big blocks of code into small modules/components, in order to make these last ones as much reusable as possible in other applications.

Let's say we now have:

1. the EcommerceApp (an ecommerce main application)
2. a Server-file-mgr component (a component to view/manage file on server)
3. a Mylib (a library of useful functions)
4. a MailistApp (another main application to handle mail lists)

...

• EcommerceApp needs both Server-file-mgr component and Mylib to work
• Server-file-mgr needs Mylib to work
• MaillistApp needs both Server-file-mgr component and Mylib to work too.

My idea is to simply structure the SVN project folder tree putting everything at the same level:

trunk/EcommerceApp
trunk/Server-file-mgr
trunk/Mylib
trunk/MaillistApp

But in real life to make these apps to work the folder tree structure must be the following:

EcommerceApp
 |_ Mylib
 |_ Server-file-mgr

MaillistApp
 |_ Mylib
 |_ Server-file-mgr

I mean Mylib and Server-file-mgr needs to be inside the EcommerceApp/MaillistApp folder.

How would you then structure the SVN folder, as I did or in a different/better/smarter way???