As modularity developers or release engineers, we need to figure out how to flag and ideally prevent circular dependencies between modules, i.e. enforce a strict acyclic directed graph between modules in a stack, and where to put that functionality, so that we don't have to deal with all the nastiness involved with circular dependencies (difficulty to bootstrap things for example).
What other problems besides making bootstrapping difficult would this solve?
I think circular deps (once bootstrapped) are quite common and valid. Bootstrapping is a special case, doesn't happen all that often and the maintainers can usually deal with it by making temporary changes.
You may be correct.
The original thinking here was that we needed to protect the module-dep graph so that our auto-rebuild logic could be simpler.
Hmm, right, that's tricky...
It seems like (after thinking about this) that circular deps are a necessity.
The auto-rebuild stuff (coco) will just have to deal with that.
Closing this as wontfix.
@ralph changed the status to Closed
Closed
Login to comment on this ticket.