I have used ZF in several projects, and think is is quite safe to use svn:externals to attach Zend and ZendX as external dependency. It might not be the good idea for other projects, but when it comes to ZF – what is in trunk is pretty stable.
So, go into folder which stores ZF, and safely remove the library. Then just add ZF as external dependency (which would be updated every time you update the working copy):
svn pe svn:externals .
in and editor opened, enter the dependencies:
Zend http://framework.zend.com/svn/framework/standard/trunk/library/Zend ZendX http://framework.zend.com/svn/framework/extras/trunk/library/ZendX
finally commit everything and obtain.
svn ci -m 'ZF set as external dep' svn up
The beauty of this approach – you always have up to date version of ZF.
The danger of this approach – you always have up to date version of ZF!
Word of caution:
Sometimes this may break things (when backward-compatibility is broken in ZF trunk), but actually if you have unit tests which check your build before deploying, you are pretty safe – you spot the problem, you resolve it.
NB: This approach supposes that you tag your releases, so that when new release is coming out, you create a tag, export everything into newly created tag (thus freezing the code), and checkout from tag on production server.
no comment untill now