Bug#306800: jta: Please allow building with sun-j2sdk1.5 and recognize the JAVA_HOME directories used by java-package

2005-04-29 Thread Kalle Kivimaa
Barry Hawkins [EMAIL PROTECTED] writes:
 The JDKs are packaged by make-jpkg are non-free, and as such, we do not
 tamper with the javac, java, etc. commands of any vendor's JRE/JDK.
 People expect that sort of thing to be left the way the vendor made it,
 and currently (for better or worse) a java command from any of them does
 not attempt to set JAVA_HOME or other environmental variables itself.

Basically what I'm wondering is what should our Java packaging policy
be related to packages requiring java2-compiler to build. Should they
check for the existence of a non-free compiler which requires the
JAVA_HOME or can they just assume the behaviour of say jikes? I think
this should be consistent and documented in the policy so that both
the maintainers and users are on the same page.

Currently the situation is that I could blindly go and close the same
bug against JSPWiki by simply saying that java2-compiler should not
require any extra environment to work and if some non-free
implementation does require that, it is not a problem of a free Debian
package. I'm not entirely comfortable with that and that's why I would
like it be consistently either JAVA_HOME supported or not.

-- 
* Sufficiently advanced magic is indistinguishable from technology (T.P)  *
*   PGP public key available @ http://www.iki.fi/killer   *



Bug#306800: jta: Please allow building with sun-j2sdk1.5 and recognize the JAVA_HOME directories used by java-package

2005-04-29 Thread Michael Koch
On Fri, Apr 29, 2005 at 10:10:09AM +0300, Kalle Kivimaa wrote:
 Barry Hawkins [EMAIL PROTECTED] writes:
  The JDKs are packaged by make-jpkg are non-free, and as such, we do not
  tamper with the javac, java, etc. commands of any vendor's JRE/JDK.
  People expect that sort of thing to be left the way the vendor made it,
  and currently (for better or worse) a java command from any of them does
  not attempt to set JAVA_HOME or other environmental variables itself.
 
 Basically what I'm wondering is what should our Java packaging policy
 be related to packages requiring java2-compiler to build. Should they
 check for the existence of a non-free compiler which requires the
 JAVA_HOME or can they just assume the behaviour of say jikes? I think
 this should be consistent and documented in the policy so that both
 the maintainers and users are on the same page.
 
 Currently the situation is that I could blindly go and close the same
 bug against JSPWiki by simply saying that java2-compiler should not
 require any extra environment to work and if some non-free
 implementation does require that, it is not a problem of a free Debian
 package. I'm not entirely comfortable with that and that's why I would
 like it be consistently either JAVA_HOME supported or not.

The Debian Policy ยง 9.9 clearly says:

A program must not depend on environment variables to get reasonable defaults.

Setting an environment variable in debian/rules for build is okay but no 
software
should depend on them during runtime. If it does we need to provide a wrapper.


Michael
-- 
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html

Join the community at http://planet.classpath.org/



Bug#306800: jta: Please allow building with sun-j2sdk1.5 and recognize the JAVA_HOME directories used by java-package

2005-04-28 Thread Andreas Jochens
Package: jta
Version: 2.5-1
Severity: wishlist
Tags: patch

Please change the Build-Depends from 'j2sdk1.4' to 'java2-compiler' to allow
building with sun-2jsdk1.5.

Please also set JAVA_HOME correctly to the directories used by the
{sun,ibm,blackdown}-j2sdk1.x packages which are created by java-package.

Regards
Andreas Jochens

diff -urN ../tmp-orig/jta-2.5/debian/control ./debian/control
--- ../tmp-orig/jta-2.5/debian/control  2005-04-28 17:49:51.881513182 +0200
+++ ./debian/control2005-04-28 17:47:44.499878134 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Java Maintainers [EMAIL PROTECTED]
 Uploaders: Jaldhar H. Vyas [EMAIL PROTECTED], Arnaud Vandyck [EMAIL 
PROTECTED]
-Build-Depends-Indep: debhelper (= 4.1), j2sdk1.4, libgnu-regexp-java, 
libcrimson-java, libjdom0-java
+Build-Depends-Indep: debhelper (= 4.1), java2-compiler, libgnu-regexp-java, 
libcrimson-java, libjdom0-java
 Standards-Version: 3.6.1
 
 Package: jta
diff -urN ../tmp-orig/jta-2.5/debian/rules ./debian/rules
--- ../tmp-orig/jta-2.5/debian/rules2005-04-28 17:49:51.881513182 +0200
+++ ./debian/rules  2005-04-28 17:39:02.0 +0200
@@ -6,18 +6,9 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH), amd64))
-   export JAVA_HOME=/usr/lib/j2sdk1.4-blackdown
-else
-   export JITC_PROCESSOR_TYPE=6
-   export JAVA_HOME=/usr/local/IBMJava2-ppc-142
-endif
-
-JAVA   =   $(JAVA_HOME)/bin/java
-JAR=   $(JAVA_HOME)/bin/jar
-JAVAC  =   $(JAVA_HOME)/bin/javac
-JAVADOC =  $(JAVA_HOME)/bin/javadoc
-JAVAH  =   $(JAVA_HOME)/bin/javah
+JAVA_HOME_DIRS=/usr/lib/j2sdk1.5-sun /usr/lib/j2sdk1.4-sun 
/usr/lib/j2sdk1.4-ibm /usr/lib/j2sdk1.4-blackdown
+export JAVA_HOME ?= $(shell for j in $(JAVA_HOME_DIRS); do [ -d $$j ]  
echo $$j  exit 0; done)
+
 export 
CLASSPATH=/usr/share/java/regexp.jar:/usr/share/java/crimson.jar:/usr/share/java/jdom0.jar
 
 configure: configure-stamp


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#306800: jta: Please allow building with sun-j2sdk1.5 and recognize the JAVA_HOME directories used by java-package

2005-04-28 Thread Kalle Kivimaa
Andreas Jochens [EMAIL PROTECTED] writes:
 Please also set JAVA_HOME correctly to the directories used by the
 {sun,ibm,blackdown}-j2sdk1.x packages which are created by java-package.

I'm of two minds about this. Isn't it really more of make-jpkg's job
to make sure that any javac built sets any required environment
variables correctly?

-- 
* Sufficiently advanced magic is indistinguishable from technology (T.P)  *
*   PGP public key available @ http://www.iki.fi/killer   *


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#306800: jta: Please allow building with sun-j2sdk1.5 and recognize the JAVA_HOME directories used by java-package

2005-04-28 Thread Andreas Jochens
On 05-Apr-28 22:13, Kalle Kivimaa wrote:
 Andreas Jochens [EMAIL PROTECTED] writes:
  Please also set JAVA_HOME correctly to the directories used by the
  {sun,ibm,blackdown}-j2sdk1.x packages which are created by java-package.
 
 I'm of two minds about this. Isn't it really more of make-jpkg's job
 to make sure that any javac built sets any required environment
 variables correctly?

I do not know a perfect solution for the JAVA_HOME problem. However,
this is a solution which is currently used by many Java related 
packages and at least it works. I do not think that JAVA_HOME should
be set by the j2sdk* packages.

Regards
Andreas Jochens


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#306800: jta: Please allow building with sun-j2sdk1.5 and recognize the JAVA_HOME directories used by java-package

2005-04-28 Thread Barry Hawkins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Kalle Kivimaa wrote:
 Andreas Jochens [EMAIL PROTECTED] writes:
 
Please also set JAVA_HOME correctly to the directories used by the
{sun,ibm,blackdown}-j2sdk1.x packages which are created by java-package.
 
 I'm of two minds about this. Isn't it really more of make-jpkg's job
 to make sure that any javac built sets any required environment
 variables correctly?
The JDKs are packaged by make-jpkg are non-free, and as such, we do not
tamper with the javac, java, etc. commands of any vendor's JRE/JDK.
People expect that sort of thing to be left the way the vendor made it,
and currently (for better or worse) a java command from any of them does
not attempt to set JAVA_HOME or other environmental variables itself.

Regards,
- --
Barry Hawkins
All Things Computed
site: www.alltc.com
weblog: www.yepthatsme.com

Registered Linux User #368650
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCcZ3gHuKcDICy0QoRArqIAJ4+Lj7GKODQAPzqxwbN3RiCWwkTCQCgnKE9
ySRLLIsy7UMEC68b5VCpd34=
=GFd/
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]