For those who used apt-get, you know that everytime you install / uninstall something, you get the notificatons saying you need / no longer need certain dependencies.
I’m trying to understand the theory behinds this and potentially implement my own version of this. I’ve done some googling, came up with mostly coupling stuff. From what I understand, coupling is 2 classes/modules that depends on each other. This is not exactly what I’m looking for. What I’m looking for is more like a dependencies tree generation, where I can find the least dependent module (I’ve already made a recursive way of doing this), and (this being the part i haven’t done) finding what’s no longer needed after removing a node.
Also, would learning about graph theory help? And is there any tutorials on that preferably using Python as a language?
Graph theory is the way to go.
A graph is just a bunch of places (vertices) with roads (edges) between them, and in particular we’re talking about a directed graph, which means one-way roads. Figuring out dependencies means, basically, finding out all the places that can reach a particular town along the one-way roads.
So now, you’ve got you bunch of modules, which become your vertices. Let’s say we have A and B, and we know B depends on A, so there’s a directed edge — a “one way road” — from A to B.
If C depends on B, then you have A→B→C.
Formally, a graph is just a collection of vertices and (ordered) pairs of vertices, called the edges. You want an graph algorithm called “topological sort”, and now you’ve got some stuff to read.