Tickets :: [#7724] Circular dependency of Util and Browser

6.0.0-beta1

11/5/25

Summary	Circular dependency of Util and Browser
Queue	Horde Framework Packages
Queue Version	HEAD
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	wrobel (at) horde (dot) org
Created	11/26/2008 (6188 days ago)
Due
Updated	11/26/2008 (6188 days ago)
Assigned
Resolved	11/26/2008 (6188 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/26/2008 09:27:57 AM	ml (at) radoeka (dot) nl	Comment #4	Reply to this comment
And in addition Horde_Browser is in fact marked as an optional dependency within package.xml. But this is not visible on its "home" page: http://pear.horde.org/index.php?package=Horde_Util&downloads As you can see there, it is just marked as a dependency. That is were I got the information from.

11/26/2008 05:34:03 AM	Gunnar Wrobel	Comment #3	Reply to this comment
And in addition Horde_Browser is in fact marked as an optional dependency within package.xml. I had no coffee yet... ;) Sorry for the noise.

11/26/2008 05:18:56 AM	Chuck Hagenbuch	Comment #2 State ⇒ Not A Bug	Reply to this comment
It's not a problem. You just have to have both packages. And this is PHP. There is no difference between runtime and build time...

11/26/2008 05:16:08 AM	Gunnar Wrobel	Comment #1 Priority ⇒ 1. Low Patch ⇒ No Milestone ⇒ Queue ⇒ Horde Framework Packages Summary ⇒ Circular dependency of Util and Browser Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
Request by Richard Bos: [Show Quoted Text - 11 lines][Hide Quoted Text] Hi Gunnar, are those dependencies correct: http://pear.horde.org/index.php?package=Horde_Util&downloads Package: Horde_Browser http://pear.horde.org/index.php?package=Horde_Browser&downloads Package: Horde_Util It looks like a circular dependency. Are these runtime dependencies or buildtime? Runtime as you usually only need PEAR for buildtime. It looks problematic to me nonetheless. If you look at the Kolab CVS spec file for Horde_Util, you see that I did not list Horde_Browser in there. I believe the use of Horde_Browser could (must) be made optional in Horde_Util.