On Thu, Jun 07, 2007 at 08:53:52PM +0200, Marcus Better wrote: > clone 427913 -1 > reassign -1 libjaxen-java > found -1 1.1.1-1 > retitle -1 libjaxen-java: circular dependency with libdom4j-java > retitle 427913 dom4j: remove jaxen code > severity 427913 normal > owner 427913 ! > owner -1 ! > tag -1 pending > thanks > > > There is a circular dependency between libdom4j-java and libjaxen-java: > > Yes. The libraries are circularly dependent. Previously we resolved that by > cutting a few classes from jaxen and pasting them into dom4j, but I reverted > that in the last upload. It wasn't very maintainable. If the classes in dom4j > ever get out of sync with the jaxen package we may get trouble, so we would > need to introduce hard versioned dependencies, which would defeat the purpose > of the whole exercise... > > I believe that jaxen should only Recommend dom4j, which should be solve the > problem, right?
As far as dpkg/apt are concerned, Recommend are merely advisory, so yes this would not cause a circular dependency. The issue is rather whether there are packages that depend only on libjaxen-java. Then they should be changed to depend on libdom4j-java. Cheers, Bill. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]