Common Include Files for Separate PHP Applications

Version control - to prevent duplication of effort

[sned]

I'm looking for opinions/thoughts about from whomever uses version control (I'm just starting to use subversion now).

I have several "applications" running on my server. Each application references files in a general includes folder (include('includes/class_Database.php'), etc.).

I want to keep my applications separate, so other users can easily download/checkout versions, but I also want prevent duplication of effort: if I change my database abstraction class, I don't want to make changes to twenty different copies of the same file.

If anyone has any ideas about this, or about using version control in a web environment in general, I'd really appreciate your input.

Thanks!
-sned

[spikey]

I have this and have a seperate repository for each application and one for the shared code. So you have to checkout your application and the shared code. I'm no subversion expert (pretty new actually) so there may be better ways of doing this. It's not really that difficult though.