[Petter Reinholdtsen] > What should the package name be? libj3d-java or libjava3d-java? Or > something else completely? Perhaps libj3d-core-java?
I've added draft build rules to pkg-java svn, <URL: svn+ssh://svn.debian.org/svn/pkg-java/trunk/java3d >. I'm not sure about naming, but have selected java3d as the source name, and libjava3d-java, libjava3d-jni and libjava3d-doc as the binary package names. Not quite sure about how to build the doc package, but the other two seem to work. I include both j3d-core and j3d-core-utils in the package, assuming both will be used together, and also because the -utils package do not have its own build rules but need to be built with j3d-core. > Is this vecmath library the same that is called libvecmath1.2-java? > I saw some comments elsewhere claiming libvecmath1.2-java is > incompatible with Java3D. If this is the case, how should be handle > the conflict? The SUN vecmath library is not the same as libvecmath1.2-java. The latter is based on an old version of the specification of vecmath and have not been developed since 1999. As the SUN vecmath library is free software now, I would recommend dropping libvecmath1.2-java and replace it with the SUN vecmath library. Any comments on this? Should it in this case provide libvecmath1.2-java for those using the existing package, or should we migrate them over? Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]