The whole idea of java-gcj-compat[-dev/-plugin] is to recreate the traditional jre/jdk folder structure.
In this case there is the still official GCJ-4.1 version, and the new/unreleased GCJ-4.2 version but with a lot of new stuff (that's why there is GCJ-4.2 available in the repos). Why not define two java-gcj-compat packages, similar to the two GCJ packages? We could have the packages: - java-gcj-compat[-dev/-plugin]-4.1 Which should depend on: - GCJ 4.1 - GIJ 4.1 - libgcj7 - gcjwebplugin-4.1 and the packages: - java-gcj-compat[-dev/-plugin]-4.2 Which should depend on: - GCJ 4.2 - GIJ 4.2 - libgcj8 - gcjwebplugin-4.2 Then, the packages java-gcj-compat[-dev/plugin] should depend on java- gcj-compat[-dev/plugin]-4.1. This way users wanting to test applications on GCJ-4.2 can use the expected java compatibility layer. rivas -- java-gcj-compat(-dev/-plugin) should depend on newer packages https://launchpad.net/bugs/63792 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
