Oops, did not check libgcj7-dev, there the hard-dependency is. But in a way it is in a way logical since gui is one of the features why java got popular (I know, there are a lot of other reasons, but it is). The only sane solution I see at the moment would be, to make a libgcj7-awt-dev (or a libgcj7-nogui-dev) package and remove the awt-stuff from libgcj7-dev (what with the first solution would cause at least a lot of build-deps to be updated). The GTK-dependency is due the fact that gcj only provides a GTK-based AWT implementation at the moment.
For I'm not really a Java-programmer (but I tried a few years ago to become one ;-)) I may be wrong, but as far as I remember AWT is an integral part of the java-language that is assumed to be present in a java-develop-environment. If this is the case (CS 1 guides at least assume the presence), another behaviour as the present would rather be undesirable. -- gcj dependencies seem unreasonable https://launchpad.net/bugs/62483 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
