>I meant the man who will make the Debian package of Tomcat. According >to the Debian philosophy, it means making different packages and >dependencies. The packages with license problems will not be IN a >package but an installer package may be a good solution (the >[end-]user will be prompted by DebConf to download the package from >the Sun site (login and/or accepting license terms) and then place the >downloaded zip file in /tmp, the installer package will extract the >zip file and place it in /usr/share/java).
Another solution could be to have the Sun jars allready present on the build machine and put them in binary package (it's allowed), via a custom build.properties. I don't know deb packaging but on Redhat RPM we could add a require for /usr/share/java/jndi.jar, /usr/share/java/jta.jar .... tyrex is free but also require jta to be built, so it's the same problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]