Isn't it only np complete if you *don't* allow multiple versions per library? That's what I remember at least 
-
-
-
Hah, yeah maybe? I can see "dependency flattening" causing similar problems though, and that seems to be a relevant optmization for most package managers haha.
- 1 more reply
New conversation -
-
-
In practice, though, any realistic dependency management problem is usually trivially solvable with a brute force search.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think it depends on the exact requirements; if you require only a single, unique version of each package in a dependency graph, it becomes NP complete. I think that’s why it would make so much sense to separate packages into public and private dependencies.
-
That reduces the subset of constrains to be satisfied to just the public ones. If you don’t expose the API of your private ones, they can co-exist and ”anything goes”. (Of course it’s still worthwhile to try and unify dependencies, if only for binary/code size.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.