You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that Docblox has some dependencies to these projects, it should be documented somewhere.
now that we have pear package we could suggest to the users to do:
pear channel-discover pear.symfony-project.com
pear install symfony/symfony
pear channel-discover pear.zfcampus.org
pear install zfcampus/zf
Tyrael
The text was updated successfully, but these errors were encountered:
I definitely agree that the dependencies should be documented; as for the PEAR channels. I am inclined not to use the symfony dependency (I only use the sfTimer class) as this will generate too much overhead in my opinion.
Concerning the Zend Framework dependency am I currently inquiring with Ralph Schindler how reliable that is. If it is, I'd be more than happy to remove the ZF components from the PEAR packaging and add a dependency there.
I would like to keep them for the downloadable version on Github but I need to find a way to change the autoloading so that it does not need to know where Zend is.
Once I change this part I will also remove the Pear_Graphviz which is in the lib folder and add it as a dependency.
This was fixed in v0.9.5 (which I just released); the Zend, Markdown and GraphViz packages are now dependencies of the PEAR package and are no longer packaged
I've noticed that Docblox has some dependencies to these projects, it should be documented somewhere.
now that we have pear package we could suggest to the users to do:
pear channel-discover pear.symfony-project.com
pear install symfony/symfony
pear channel-discover pear.zfcampus.org
pear install zfcampus/zf
Tyrael
The text was updated successfully, but these errors were encountered: