I have a need to create a library of Object Oriented PHP code that will see much reuse and aspires to be highly flexible and modular. Because of its independent nature I would like it to exist as its own SVN project.

I would like to be able to create a new web project, save it in SVN as its own separate project, and include within it the library project code as well. During this process, while coding the web application code and making commits, I may need to add a class to the library. I would like to be able to do so and commit those changes back to the libraries project code.

In light of all this I could manage the code in two ways

1. Commit the changes to the library back to a branch of its original base project code and make the branch name relevant to the web project I was using it with

2. Commit the changes to the library back to the original code, growing it in size regardless of any specific references that might exist.

I have two questions

• How can I include this library project code into a new project yet not break the subversion functionality, i.e. allowing me to make changes to each project individually?

• How I can keep the code synchronized? If I choose the first method of managing the library code I may want to grab changes from another branch and pull it in for use in another.