Hallo Stefan,
* Stefan Gybas wrote:
>You are a package manager, not a "standard" user. You should have a lot
>of differnt JDK installed anyway to be ably to very bug reports so
>what's the problem with on specific JDK in build dependencies?
Almost half of the bugs/mails about eclipse ended in t
Hallo Stefan,
* Stefan Gybas wrote:
>You are a package manager, not a "standard" user. You should have a lot
>of differnt JDK installed anyway to be ably to very bug reports so
>what's the problem with on specific JDK in build dependencies?
Almost half of the bugs/mails about eclipse ended in t
Jan Schulz wrote:
I'm doing it all the time: I'm running woody and I have specified
deb ... stable
deb-src ... unstable
You are a package manager, not a "standard" user. You should have a lot
of differnt JDK installed anyway to be ably to very bug reports so
what's the problem with on specific JD
Hallo Stefan,
* Stefan Gybas wrote:
>>I've had a look at this bug and I thing we should not fource a
>>specific javac or java at our users. If they don't want to download a
>>BD JDK, then this should be made possible.
>It is just for building the package. I don't think that most users will
>rebui
Jan Schulz wrote:
I've had a look at this bug and I thing we should not fource a
specific javac or java at our users. If they don't want to download a
BD JDK, then this should be made possible.
It is just for building the package. I don't think that most users will
rebuild the Java packages, espec
Jan Schulz wrote:
I'm doing it all the time: I'm running woody and I have specified
deb ... stable
deb-src ... unstable
You are a package manager, not a "standard" user. You should have a lot
of differnt JDK installed anyway to be ably to very bug reports so
what's the problem with on specific J
Hallo Stefan,
* Stefan Gybas wrote:
>>Excellent! ;) Can I copy/paste it in mine? ;)
I've also just inherited this code... :)
>I've written this code 2 years ago when Blackdown changed their
>JAVA_HOME in the j2sdk1.3 packages from /usr/lib/j2sdk1.3 to
>/usr/lib/j2se/1.3 so packages could be bu
Hallo Stefan,
* Stefan Gybas wrote:
>>I've had a look at this bug and I thing we should not fource a
>>specific javac or java at our users. If they don't want to download a
>>BD JDK, then this should be made possible.
>It is just for building the package. I don't think that most users will
>rebui
Hallo Stefan,
* Stefan Gybas wrote:
>Jan Schulz wrote:
>In eclipse? I think #197484 is a perfect example why this is bad and why
>you should use one specific JDK version.
Yep, that one was bad. But I don't think that I want to install a
specific JDK just for compiling. OK, I've curently 5 JDKs i
Arnaud Vandyck wrote:
Excellent! ;) Can I copy/paste it in mine? ;)
No, please don't!
I've written this code 2 years ago when Blackdown changed their
JAVA_HOME in the j2sdk1.3 packages from /usr/lib/j2sdk1.3 to
/usr/lib/j2se/1.3 so packages could be build with both versions (see
#122584). It ist
Jan Schulz wrote:
I've had a look at this bug and I thing we should not fource a
specific javac or java at our users. If they don't want to download a
BD JDK, then this should be made possible.
It is just for building the package. I don't think that most users will
rebuild the Java packages, espe
Jan Schulz wrote:
I'm currently using this line to get 'java' in debian/rules:
jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3 /usr/lib/j2sdk1.3
JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \
then echo \
$$jdir;exit 0;fi;done)
In eclipse? I think #197484 is a
Jan Schulz <[EMAIL PROTECTED]> wrote:
[...]
> I'm currently using this line to get 'java' in debian/rules:
> jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3
> /usr/lib/j2sdk1.3
> JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \
> then echo \
> $$jdir;exit 0;fi
Hallo Stefan,
* Stefan Gybas wrote:
>>Excellent! ;) Can I copy/paste it in mine? ;)
I've also just inherited this code... :)
>I've written this code 2 years ago when Blackdown changed their
>JAVA_HOME in the j2sdk1.3 packages from /usr/lib/j2sdk1.3 to
>/usr/lib/j2se/1.3 so packages could be bu
Hallo Arnaud,
* Arnaud Vandyck wrote:
>Stefan Gybas <[EMAIL PROTECTED]> wrote:
>What are the possible values of JAVA_HOME where you want to use
>something different from Blackdown's or Sun's JDK?
There are a lot IMO:
The values, where mpkg-j2sdk puts the JDKs, /usr/local... and so on.
I
Hallo Stefan,
* Stefan Gybas wrote:
>Jan Schulz wrote:
>In eclipse? I think #197484 is a perfect example why this is bad and why
>you should use one specific JDK version.
Yep, that one was bad. But I don't think that I want to install a
specific JDK just for compiling. OK, I've curently 5 JDKs i
Hallo Ben,
* Ben Burton wrote:
>> I agree with this. IMO a java jar should be handled the same as a
>> binary lib ad should get API Version (~SONAME) included in its name.
>The problem is that many java libraries don't have a concept of an API
>version / soname. All you can guarantee to get is a
Arnaud Vandyck wrote:
Excellent! ;) Can I copy/paste it in mine? ;)
No, please don't!
I've written this code 2 years ago when Blackdown changed their
JAVA_HOME in the j2sdk1.3 packages from /usr/lib/j2sdk1.3 to
/usr/lib/j2se/1.3 so packages could be build with both versions (see
#122584). It i
Jan Schulz wrote:
I'm currently using this line to get 'java' in debian/rules:
jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3 /usr/lib/j2sdk1.3
JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \
then echo \
$$jdir;exit 0;fi;done)
In eclipse? I think #197484 is
Jan Schulz <[EMAIL PROTECTED]> wrote:
[...]
> I'm currently using this line to get 'java' in debian/rules:
> jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3 /usr/lib/j2sdk1.3
> JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \
> then echo \
> $$jdir;exit 0;fi;do
Hallo Arnaud,
* Arnaud Vandyck wrote:
>Stefan Gybas <[EMAIL PROTECTED]> wrote:
>What are the possible values of JAVA_HOME where you want to use
>something different from Blackdown's or Sun's JDK?
There are a lot IMO:
The values, where mpkg-j2sdk puts the JDKs, /usr/local... and so on.
I
Andrew Pimlott wrote:
You might want official builds to always use the same compiler, but
there's no reason not to make it convenient for others to use their
preferred compiler. Especially when the preferred compiler is
proprietary. We should be moving away from hard-coding knowledge
about the co
Hallo Ben,
* Ben Burton wrote:
>> I agree with this. IMO a java jar should be handled the same as a
>> binary lib ad should get API Version (~SONAME) included in its name.
>The problem is that many java libraries don't have a concept of an API
>version / soname. All you can guarantee to get is a
On Mon, Jul 28, 2003 at 07:13:47PM +0200, Stefan Gybas wrote:
> That's exactly the purpose. A build dependency for a JVM should be
> specific, see http://pkg-java.alioth.debian.org/building.html for the
> reasons.
You might want official builds to always use the same compiler, but
there's no rea
Andrew Pimlott wrote:
You might want official builds to always use the same compiler, but
there's no reason not to make it convenient for others to use their
preferred compiler. Especially when the preferred compiler is
proprietary. We should be moving away from hard-coding knowledge
about the c
On Mon, Jul 28, 2003 at 07:13:47PM +0200, Stefan Gybas wrote:
> That's exactly the purpose. A build dependency for a JVM should be
> specific, see http://pkg-java.alioth.debian.org/building.html for the
> reasons.
You might want official builds to always use the same compiler, but
there's no rea
Stefan Gybas <[EMAIL PROTECTED]> wrote:
> Daniel Bonniot wrote:
> > It's best to have both options. Otherwise it forces every package to
> > build-depend on a specific JVM, even though some might work with any
> > JVM.
>
> That's exactly the purpose. A build dependency for a JVM should be
> sp
Daniel Bonniot <[EMAIL PROTECTED]> wrote:
>
> >I was playing with this a few weeks ago. It's a shame it doesn't support
> >mouse or keyboard.
> >
> Taken from their main webpage:
> CHARVA now also has mouse support on terminal-emulators that report
> mouse events, such as "xterm" and "PuTTY
> <
Adam Heath <[EMAIL PROTECTED]> wrote:
> On Mon, 28 Jul 2003, Arnaud Vandyck wrote:
[...]
> > Description : internationalization library for java
> > This library is needed by ArgoUML.
> That's no excuse for not writing a proper description.
Have you seen the website?! ;)
OK, I'll work on a
Stefan Gybas <[EMAIL PROTECTED]> wrote:
> Daniel Bonniot wrote:
> > It's best to have both options. Otherwise it forces every package to
> > build-depend on a specific JVM, even though some might work with any
> > JVM.
>
> That's exactly the purpose. A build dependency for a JVM should be
> sp
Daniel Bonniot <[EMAIL PROTECTED]> wrote:
>
> >I was playing with this a few weeks ago. It's a shame it doesn't support
> >mouse or keyboard.
> >
> Taken from their main webpage:
> CHARVA now also has mouse support on terminal-emulators that report
> mouse events, such as "xterm" and "PuTTY
> <
Adam Heath <[EMAIL PROTECTED]> wrote:
> On Mon, 28 Jul 2003, Arnaud Vandyck wrote:
[...]
> > Description : internationalization library for java
> > This library is needed by ArgoUML.
> That's no excuse for not writing a proper description.
Have you seen the website?! ;)
OK, I'll work on a
32 matches
Mail list logo
