Code review comment for lp:~didrocks/autopilot/remove-circular-dep

From http://www.debian.org/doc/debian-policy/ch-relationships.html (7.2 Binary Dependencies):

"If there is a circular dependency among packages being installed or removed, installation or removal order honoring the dependency order is impossible, requiring the dependency loop be broken at some point and the dependency requirements violated for at least one package. Packages involved in circular dependencies may not be able to rely on their dependencies being configured before they themselves are configured, depending on which side of the break of the circular dependency loop they happen to be on. If one of the packages in the loop has no postinst script, then the cycle will be broken at that package; this ensures that all postinst scripts are run with their dependencies properly configured if this is possible. Otherwise the breaking point is arbitrary. Packages should therefore avoid circular dependencies where possible, particularly if they have postinst scripts."

Yeah, as you can see, it's not an issue as of today, BUT, maybe one day, you will have subtile configuration issue and we'll have forgotten about the circular dependency. That's why following the debian policy: we should therefore avoid them