Managing a core library in Subversion

Question

This is giving me major headaches! I'm having trouble even describing the problem in words.

Basically, I want to be able to manage a core library (coreLib) of Actionscript classes with the following requirements:

• latest version is checked out when a new project starts.
• a dev can make changes to the coreLib and then commit them back into the repo as project is written (maybe bug-fixes, added features, etc.)
• the project contains a 'snapshot' of the coreLib so that, if returned to months later, it (as automatically as possible) has a copy of the coreLib that has guaranteed compatibility with the project.

I tried using externals but this can break compatibility going backwards. I'm currently exporting the coreLib into the project and its VC'd along with the project. I can't figure out how to get the changes back into the repo though, without just copying over the top and losing history.

Any advice?

Answer 1

How exactly are svn:externals breaking compatibility going backwards? You can link svn:externals to a specific revision so that when you go back in the history your project is linked with the correct version of the library.

See also my answer in the question SVN: Release branch and externals?

Answer 2

I think the simpliest approach would be to manage all ActionScript projects and your core library in one single repository.

Answer 3

You've got one 'path/folder' for your core library, that is used as trunk. Why not just copying your 'core library trunk' into your project folder? This is nothing else than a branch from your 'core library trunk', living in your project folder.

Developers may alter their core library branch without breaking any dependencies. Merging forth and back between 'core library trunk' and 'core library project branches' can be done without side effects.

-lib
-project1
 -lib(branch project 1)
-project2
 -lib(branch project 2)