Hi. Your pointer wasn't very useful. It was a pointer to examples of circular dependencies, not what breaks on upgrades, so it was not useful for me in trying to balance problems potentially created by the circular dependency against potential solutions.
Do you have any suggestions on how to deal with it in this case? libverto-glib1 and libverto-libev1 are basically plugins into libverto. It's possible although unlikely for an application to link directly against one of these plugin libraries. Recommends is definitely not a good solution: software such as the not-yet-uploaded krb5-kdc 1.10 would be completely disfunctional if there were no valid libverto module installed. I could stick one of the plugins in the libverto1 package. That's a violation of a should in policy and would create significant problems if the plugin in question ever disappeared from libverto when the soname was not otherwise changing. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
