I've been working on packaging the Java code and was somewhat surprised with the amount of dependencies that our code (client + broker) currently has. "Dependencies" in this context should be viewed as "requires" and "build requires" for rpm deployment and building, i.e., all the packages that need to be installed before qpid can be itself installed or built.

This points to a graph of a *partial* dependency tree: http://people.redhat.com/nsantos/graph.png

The original tree is much larger, but I've excluded maven2 and all its dependencies, as well as packages that are already in Fedora 7 (which takes care of things like ant, saxon, among many others). Still, this leaves a long list of 40 packages.

It's been pointed out to me that some of these dependencies may be lingering artifacts from stuff that was once used but is no more... if any of you can identify specific instances of such packages, or suggest other ways to prune the tree, I'd truly appreciate it.

Thanks,
Nuno

Reply via email to