External SVN Resources and Export for Framework

I am currently working on a wireframe for a client. The framework is based on Zend Framework. Directory structure:

application: Application specific code
application / modules / frontend: Application specific code
application / modules / backend: Backend for MyFramework
library / MyFramework: The custom framework
library / Zend: The Zend framework
public: Images, CSS, JavaScript
test: Tests (also includes tests for MyFramework)

I need to find a way to manage this project with Subversion. We want MyFramework and Zend to be loaded externally because the client doesn't need to update this code. The app and public folder must also be downloaded from Subversion, but can be modified by the client.

When a client starts working on a new application, they must export the complete folder structure:

svn export svn://complete_framework

      

The export is necessary because they will be putting the code into their own Subversion for version control. When exporting, external values ​​for Zend and MyFramework are lost, so they need to be added.

Does Subversion offer any solution for this, or should we just write a shell script that exports and re-installs the external elements?

+2


source to share


2 answers


A distributed system will do much better in your test case. Anyway, does it help to svn export --ignore-externals ...

solve the problem? I don't have multiple repos to try this on my own.



+1


source


See if your script fits Vendor Branches .



+1


source







All Articles