Hi
Correcttion to myself. Sorry.
*SNIP*
If you change java-runtime to java1-runtime it is perfectly correct.
Can everyone agree that this is correct? If not, can someone suggest a
line that will satisfy everyone?
But you do not need to depend on any of the above except java-common
if
Stephen Also, WTF is with all the Architecture: all' -java packages
Stephen that only depend on java-common? While I guess they're
Stephen installable without a java runtime on this system, they're a
Stephen completely unusable in that sate.
I made this point when Ola discussed the java policy.
Followups set to debian-java where this is a little more on topic.
Ian == Ian Zimmerman [EMAIL PROTECTED] writes:
Ian gcj can compile java bytecode into native code. So
Ian Architecture: all java libraries can be used for development
Ian purposes without an interpreter.
Yes, and I
Stephen == Stephen Zander [EMAIL PROTECTED] writes:
Stephen Followups set to debian-java where this is a little more
Stephen on topic.
Excpet that I forgot to actually set the header. Bah.
--
Stephen
And what do we burn apart from witches?... More witches!
--
To UNSUBSCRIBE, email
Ola == Ola Lundqvist [EMAIL PROTECTED] writes:
So, here's my (hopefully) final question. I think I have
addressed everyone's concerns with this Depends line:
Depends: kaffe | java-virtual-machine, kaffe | java-runtime,
java-common
Ola If you change java-runtime to
Ola == Ola Lundqvist [EMAIL PROTECTED] writes:
Ola This looks good if you only need a virtual machine and it
Ola works with kaffe. But you most probably need a java1-runtime
Ola to run it (not jus kaffe) so you should add that too (if you
Ola need the runtime classes).
While I
On Thu, Nov 21, 2002 at 11:16:21AM -0600, Kenneth Pronovici wrote:
So, here's my (hopefully) final question. I think I have addressed
everyone's concerns with this Depends line:
Depends: kaffe | java-virtual-machine, kaffe | java-runtime, java-common
Can everyone agree that this is
Hi
On Thu, Nov 21, 2002 at 11:16:21AM -0600, Kenneth Pronovici wrote:
Ok... I've gotten a lot of answers on this thread, which I REALLY
appreciate. This is what I love about Debian. :-) I just want to take
one last pass at my question, to make sure everyone's in agreement.
Parts of this
Hi
Correcttion to myself. Sorry.
*SNIP*
If you change java-runtime to java1-runtime it is perfectly correct.
Can everyone agree that this is correct? If not, can someone suggest a
line that will satisfy everyone?
But you do not need to depend on any of the above except java-common
if
From policy:
Java libraries must depend on the needed runtime environment (java1-runtime
and/or java2-runtime) but should not depend (only suggest)
java-virtual-machine.
Right. I will use this:
Depends: kaffe | java1-runtime, java-common
Suggests: java-virtual-machine
I think that
Ola == Ola Lundqvist [EMAIL PROTECTED] writes:
So, here's my (hopefully) final question. I think I have
addressed everyone's concerns with this Depends line:
Depends: kaffe | java-virtual-machine, kaffe | java-runtime,
java-common
Ola If you change java-runtime to
Stephen Also, WTF is with all the Architecture: all' -java packages
Stephen that only depend on java-common? While I guess they're
Stephen installable without a java runtime on this system, they're a
Stephen completely unusable in that sate.
I made this point when Ola discussed the java policy.
Followups set to debian-java where this is a little more on topic.
Ian == Ian Zimmerman [EMAIL PROTECTED] writes:
Ian gcj can compile java bytecode into native code. So
Ian Architecture: all java libraries can be used for development
Ian purposes without an interpreter.
Yes, and I
Stephen == Stephen Zander [EMAIL PROTECTED] writes:
Stephen Followups set to debian-java where this is a little more
Stephen on topic.
Excpet that I forgot to actually set the header. Bah.
--
Stephen
And what do we burn apart from witches?... More witches!
Ok... I've gotten a lot of answers on this thread, which I REALLY
appreciate. This is what I love about Debian. :-) I just want to take
one last pass at my question, to make sure everyone's in agreement.
Parts of this thread (which is now a week+ long) have gotten lost along
the way :), so to
On Wed, Nov 20, 2002 at 01:58:45PM +0100, Sven Luther wrote:
BTW, i have tried to install the J2sdk1.4 packages, but they complain
about a missing j2se-common.
Add main to sources.list along with non-free.
--
Colin Watson [[EMAIL PROTECTED]]
--
To
On Sat, Nov 16, 2002 at 10:21:55AM +0100, Sven Luther wrote:
In the original version of my package, I just listed a Depends on
java-common. Is this still appropriate, even though I know that not
every package that provides java-common will work with my package?
Hi
java-common is NOT a
On Wed, Nov 20, 2002 at 01:43:10PM +0100, Ola Lundqvist wrote:
On Sat, Nov 16, 2002 at 10:21:55AM +0100, Sven Luther wrote:
In the original version of my package, I just listed a Depends on
java-common. Is this still appropriate, even though I know that not
every package that provides
Sven == Sven Luther [EMAIL PROTECTED] writes:
Sven BTW, i have tried to install the J2sdk1.4 packages, but they
Sven complain about a missing j2se-common. Is this the same
Sven package as java-common ?
Someone else already metioned it but you needto add main to you
bacldown mirror
On Wed, Nov 20, 2002 at 07:49:10AM -0800, Stephen Zander wrote:
Sven == Sven Luther [EMAIL PROTECTED] writes:
Sven BTW, i have tried to install the J2sdk1.4 packages, but they
Sven complain about a missing j2se-common. Is this the same
Sven package as java-common ?
Someone else
You should list the working package first :
working-java | java-common
And it should look like this instead.
working-jvm | java-virtual-machine.
Ok. I will change it to:
Depends: kaffe | java-virtual-machine, java-common
Is this correct?
KEN
--
Kenneth J. Pronovici [EMAIL
Hi KEN,
-Original Message-
From: Kenneth Pronovici [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 2:10 AM
To: Ola Lundqvist; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: j2sdk build-depends cannot be satisfied?
Ok. I will change
$ apt-cache show kaffe
..snip..
Provides: java-virtual-machine, java-runtime, java1-runtime
So, kaffe provides java-virtual-machine. You don't need to write dependency
for kaffe.
Ok, that makes sense.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
Personal Homepage:
okamototk == okamototk [EMAIL PROTECTED] writes:
Hi KEN,
-Original Message-
From: Kenneth Pronovici [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 2:10 AM
To: Ola Lundqvist; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: j2sdk build-depends cannot be satisfied
On Wed, Nov 20, 2002 at 01:43:10PM +0100, Ola Lundqvist wrote:
On Sat, Nov 16, 2002 at 10:21:55AM +0100, Sven Luther wrote:
In the original version of my package, I just listed a Depends on
java-common. Is this still appropriate, even though I know that not
every package that provides
On Wed, Nov 20, 2002 at 01:58:45PM +0100, Sven Luther wrote:
BTW, i have tried to install the J2sdk1.4 packages, but they complain
about a missing j2se-common.
Add main to sources.list along with non-free.
--
Colin Watson [EMAIL PROTECTED]
Sven == Sven Luther [EMAIL PROTECTED] writes:
Sven BTW, i have tried to install the J2sdk1.4 packages, but they
Sven complain about a missing j2se-common. Is this the same
Sven package as java-common ?
Someone else already metioned it but you needto add main to you
bacldown mirror
You should list the working package first :
working-java | java-common
And it should look like this instead.
working-jvm | java-virtual-machine.
Ok. I will change it to:
Depends: kaffe | java-virtual-machine, java-common
Is this correct?
KEN
--
Kenneth J. Pronovici [EMAIL
Hi KEN,
-Original Message-
From: Kenneth Pronovici [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 21, 2002 2:10 AM
To: Ola Lundqvist; debian-java@lists.debian.org;
debian-mentors@lists.debian.org
Subject: Re: j2sdk build-depends cannot be satisfied?
Ok. I will change
$ apt-cache show kaffe
..snip..
Provides: java-virtual-machine, java-runtime, java1-runtime
So, kaffe provides java-virtual-machine. You don't need to write dependency
for kaffe.
Ok, that makes sense.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
Personal Homepage:
-depends cannot be satisfied?
Ok. I will change it to:
Depends: kaffe | java-virtual-machine, java-common
Is this correct?
$ apt-cache show kaffe
..snip..
Provides: java-virtual-machine, java-runtime, java1-runtime
So, kaffe provides java-virtual-machine. You don't need to write dependency
Sven == Sven Luther [EMAIL PROTECTED] writes:
Sven Yes, thanks it works fine (altough the postinst try to
Sven install the plugin to mozilla-cvs, which does not exist and
Sven thus the postinst fails)
Hmm, I'll have to look at that.
Sven Which GR ? The one about removing
If you want to specify which of a set of real packages should be the
default to satisfy a particular dependency on a virtual package, you
should list the real package as an alternative before the virtual one.
If kaffe works for Kenneth, I guess his Depends line is fine. By the
Hi
On Wed, Nov 20, 2002 at 11:10:04AM -0600, Kenneth Pronovici wrote:
You should list the working package first :
working-java | java-common
And it should look like this instead.
working-jvm | java-virtual-machine.
Ok. I will change it to:
Depends: kaffe |
: Re: j2sdk build-depends cannot be satisfied?
Ok. I will change it to:
Depends: kaffe | java-virtual-machine, java-common
Is this correct?
$ apt-cache show kaffe
..snip..
Provides: java-virtual-machine, java-runtime, java1-runtime
So, kaffe provides java-virtual-machine. You
[I think this is still topical to both debian-mentors and debian-java.
Someone tell me if they want it moved to one or the other...]
gcj is supposed to come with a working jni implementation and comes with
gij (GNU Interpreter for Java) for interpreting bytecode. What exactly
doesn't work with
On Sat, Nov 16, 2002 at 03:12:52AM -0600, Kenneth Pronovici wrote:
[I think this is still topical to both debian-mentors and debian-java.
Someone tell me if they want it moved to one or the other...]
gcj is supposed to come with a working jni implementation and comes with
gij (GNU
Hi,
On Sat, 2002-11-16 at 10:12, Kenneth Pronovici wrote:
[I think this is still topical to both debian-mentors and debian-java.
Someone tell me if they want it moved to one or the other...]
gcj is supposed to come with a working jni implementation and comes with
gij (GNU Interpreter for
Kenneth == Kenneth Pronovici [EMAIL PROTECTED] writes:
Kenneth The gij java runtime would not work for my test case (just
Kenneth some simple server/client pairs that come with the nbio
Kenneth distribution)
Bummer.
Kenneth The error I got from gij (below my signature) it a little out
Kenneth
[I think this is still topical to both debian-mentors and debian-java.
Someone tell me if they want it moved to one or the other...]
gcj is supposed to come with a working jni implementation and comes with
gij (GNU Interpreter for Java) for interpreting bytecode. What exactly
doesn't work with
On Sat, Nov 16, 2002 at 03:12:52AM -0600, Kenneth Pronovici wrote:
[I think this is still topical to both debian-mentors and debian-java.
Someone tell me if they want it moved to one or the other...]
gcj is supposed to come with a working jni implementation and comes with
gij (GNU
Hi,
On Sat, 2002-11-16 at 10:12, Kenneth Pronovici wrote:
[I think this is still topical to both debian-mentors and debian-java.
Someone tell me if they want it moved to one or the other...]
gcj is supposed to come with a working jni implementation and comes with
gij (GNU Interpreter for
Kenneth == Kenneth Pronovici [EMAIL PROTECTED] writes:
Kenneth The gij java runtime would not work for my test case (just
Kenneth some simple server/client pairs that come with the nbio
Kenneth distribution)
Bummer.
Kenneth The error I got from gij (below my signature) it a little out
Kenneth
[I'm cross-posting to debian-java and debian-mentors, because I'm not
sure whether this is a Java question or a packaging question. Please
CC me on replies, if possible.]
Can anyone suggest why libnbio2-java's build dependency on j2sdk1.3
cannot be satisfied on all 13 platforms?
On Fri, Nov 15, 2002 at 03:49:53PM -0600, Kenneth Pronovici wrote:
[I'm cross-posting to debian-java and debian-mentors, because I'm not
sure whether this is a Java question or a packaging question. Please
CC me on replies, if possible.]
Can anyone suggest why libnbio2-java's build
Last i knew, j2sdk1.3 is not part of debian, be it in main, contrib or
non-free, because it is not possible for us to distribute it because of
the licencing issues.
Because of that, this particular dependency will never be really
satisfied, the auto builders will not be able to build the
On Fri, Nov 15, 2002 at 05:00:47PM -0600, Kenneth Pronovici wrote:
Last i knew, j2sdk1.3 is not part of debian, be it in main, contrib or
non-free, because it is not possible for us to distribute it because of
the licencing issues.
Because of that, this particular dependency will never
Erm, i think it is even worse, i think that the users would need to
install the j2sdk1.3 package or else it will be unusable. This also
means that your package will never enter testing, i think, or maybe
there is some kind of override for contrib/non-free packages. Also, the
j2sdk1.3 is
Hi,
On Sat, 2002-11-16 at 01:47, Kenneth Pronovici wrote:
Mmm, another idea, java is supposed to be arch-independant bytecode, so
you should maybe build your package arch: all instead of arch: any.
Oh, I forgot to mention that... nbio is a JNI-based package (it
provides non-blocking I/O
gcj is supposed to come with a working jni implementation and comes with
gij (GNU Interpreter for Java) for interpreting bytecode. What exactly
doesn't work with gcj? Could you please file a bug report?
http://gcc.gnu.org/bugs.html
That way we at least know about the issue.
Also Kaffe,
[I'm cross-posting to debian-java and debian-mentors, because I'm not
sure whether this is a Java question or a packaging question. Please
CC me on replies, if possible.]
Can anyone suggest why libnbio2-java's build dependency on j2sdk1.3
cannot be satisfied on all 13 platforms?
On Fri, Nov 15, 2002 at 03:49:53PM -0600, Kenneth Pronovici wrote:
[I'm cross-posting to debian-java and debian-mentors, because I'm not
sure whether this is a Java question or a packaging question. Please
CC me on replies, if possible.]
Can anyone suggest why libnbio2-java's build
Last i knew, j2sdk1.3 is not part of debian, be it in main, contrib or
non-free, because it is not possible for us to distribute it because of
the licencing issues.
Because of that, this particular dependency will never be really
satisfied, the auto builders will not be able to build the
On Fri, Nov 15, 2002 at 05:00:47PM -0600, Kenneth Pronovici wrote:
Last i knew, j2sdk1.3 is not part of debian, be it in main, contrib or
non-free, because it is not possible for us to distribute it because of
the licencing issues.
Because of that, this particular dependency will never
Erm, i think it is even worse, i think that the users would need to
install the j2sdk1.3 package or else it will be unusable. This also
means that your package will never enter testing, i think, or maybe
there is some kind of override for contrib/non-free packages. Also, the
j2sdk1.3 is
Hi,
On Sat, 2002-11-16 at 01:47, Kenneth Pronovici wrote:
Mmm, another idea, java is supposed to be arch-independant bytecode, so
you should maybe build your package arch: all instead of arch: any.
Oh, I forgot to mention that... nbio is a JNI-based package (it
provides non-blocking I/O
gcj is supposed to come with a working jni implementation and comes with
gij (GNU Interpreter for Java) for interpreting bytecode. What exactly
doesn't work with gcj? Could you please file a bug report?
http://gcc.gnu.org/bugs.html
That way we at least know about the issue.
Also Kaffe,
57 matches
Mail list logo
