On Tue, Mar 22, 2011 at 3:41 PM, Bruno Haible <br...@clisp.org> wrote:
> I think, on the contrary, it would be essential to show all paths, > otherwise the user does work to cut a dependency and then afterwards notices > that there are other paths to the particular dependency that are much > harder to cut. so, my first shell script didn't show all paths. I wasn't satisfied with the results or the speed of the shell script http://gitorious.org/gnulib-module-graph/gnulib-module-graph I pushed this ugly bit of code here it really needs a clean up but it works, is able to output graphs of individual modules, and combined graphs of multiple modules, see the README/INSTALL.git if someone wants me to add something like all paths that can cause a module to be included, i can add that too. If you guys want to include it in gnulib thats fine (should have a copyright assignment on file), if not that is fine also. > All this is in the area of graph display, where the graph is a Directed > Acyclic Graph and 'gnulib-tool --extract-dependencies' provides the links > between nodes. I won't have time to plunge into this; volunteers welcome. Actually, it's not acyclic, there is a cycle xalloc and xalloc-die.
