Hi Andries!
Since we not only use ZF, we had similar Problems.
Our approach is not really a solution for that, we just figured there
is no other way in handling this.
Therefore our structure looks like this:
/http: www_document_root
/lib/php: here are the externals and the project
/lib/php/Zend: links to a tagged version of the Zend/library (not incubator)
/lib/php/OwnFramework: links to a tag of our own framework (which held
only a configuration setup for our system)
/lib/php/Smarty
...
/lib/php/ProjectName: here is the application with its specific classes.
We use only tagged version for our projects because we don't recheck
everytime something has changed somewhere, the projects have to be
stable.
For our project setup we have some scripts autogenerating the correct
paths for apache so we don't have to do much handwork.
bests, thomas
On 2/23/07, Ramon de la Fuente <
[hidden email]> wrote:
> Hi Andries,
>
> I currently import the Zend_Framework completely from SVN to it's own
> directory, and add the path to the "Zend_Framework/library" folder to
> php_path with a .htaccess directive. This means I maintain only 1
> framework folder for all projects, and leaves me free to add a 'lib'
> folder to projects with project-specific libraries. (it also leaves room
> to include incubator classes by adding the incubator/library to the path
> as well).
>
> After a projects goes live and everything moves to a live webserver, all
> I have to do is upload the current (at that time) Zend folder and
> Zend.php file into the "lib" directory inside the project.
>
> Cheers,
>
> Ramon
>
>
> Andries Seutens wrote:
> >
> > Dear all,
> >
> > I am using some of Zend's libraries in several projects. To keep
> > everything up to date, I am *using* svn:externals as follows:
> >
> > svn propedit svn:externals .
> > lib/
http://framework.zend.com/svn/framework/trunk/library> >
> > Turns out that this isn't possible, because any directory you specify
> > for an svn:externals checkout should not already exist in the
> > repository. Apperently in my case, the folder lib already exist, and
> > I'm using it to store other libraries.
> >
> > So this leads to an svn error (because the libs folder already exist):
> >
> > svn: Working copy 'libs' locked
> > svn: run 'svn cleanup' to remove locks
> >
> > What I could do is:
> >
> > svn propedit svn:externals .
> > lib/Zend
http://framework.zend.com/svn/framework/trunk/library> >
> > but this will create a "Zend" folder, which in turn contains a "Zend"
> > folder with the actual ZF libraries. I like to keep my files
> > organized, so this solution
> > isn't really what I am looking for.
> >
> > What I did now is:
> >
> > svn propedit svn:externals .
> > lib/Zend
http://framework.zend.com/svn/framework/trunk/library/Zend/> >
> > Again, this brings me a big con, because now I don't have the file
> > "Zend.php" in my svn:externals.
> >
> > Has anybody experienced the same problems? Or does anyone has a
> > solution for this scenario?
> >
> > Best,
> >
> >
> > ------------------------------------------------------------------------
> >
> > Gecontroleerd op virussen door de JOJO Secure Gateway.
> >
>
>
>
--
"Power corrupts. Power failure corrupts absolutely"
