On Tue, 3 Apr 2001, Stephane Bortzmeyer wrote:
> As I announced here, I've formally orphaned my Java-related programs,
> specially java-common.
> Muffin is a nice program. A shame it does not run with free
> software :-(
Yes, I'd agree - I'd really like to adopt Muffin, if it hasn't
been picked
On Tue, 3 Apr 2001, Stephane Bortzmeyer wrote:
> As I announced here, I've formally orphaned my Java-related programs,
> specially java-common.
> Muffin is a nice program. A shame it does not run with free
> software :-(
Yes, I'd agree - I'd really like to adopt Muffin, if it hasn't
been picked
On Tue, Apr 03, 2001 at 10:24:59PM +0200, Stephane Bortzmeyer wrote:
>
> Package: wnpp
> Severity: normal
>
> In my new job, I no longer use or teach Java. Besides, I'm quite
> disappointed with the way free Java works (or does not work) and I'm
> fed up with the hype about Java, which invariab
[Please Cc: me the replies, I'm no longer on the debian-java list.]
As I announced here, I've formally orphaned my Java-related programs,
specially java-common.
In my new job, I no longer use or teach Java. Besides, I'm quite
disappointed with the way free Java works (or does not work) and I'm
[EMAIL PROTECTED] (Andrew Pimlott) writes:
> > JNI libraries shold probably (by default) go in either /usr/lib
> > or /usr/lib/java. The latter again has the advantage of reducing
> > clutter and name clashes, but I don't know how awkward that would
> > be for other Java implementations.
>
> Ok,
On Tue, Apr 03, 2001 at 10:24:59PM +0200, Stephane Bortzmeyer wrote:
>
> Package: wnpp
> Severity: normal
>
> In my new job, I no longer use or teach Java. Besides, I'm quite
> disappointed with the way free Java works (or does not work) and I'm
> fed up with the hype about Java, which invaria
Ok, it looks like my understanding of the details is lacking. I'll
try to keep this message on a higher level. Sorry for any
confusion.
On Tue, Apr 03, 2001 at 08:58:19AM -0700, Per Bothner wrote:
> [EMAIL PROTECTED] (Andrew Pimlott) writes:
> > On the other hand, if JNI is an ABI, it would
> >
[Please Cc: me the replies, I'm no longer on the debian-java list.]
As I announced here, I've formally orphaned my Java-related programs,
specially java-common.
In my new job, I no longer use or teach Java. Besides, I'm quite
disappointed with the way free Java works (or does not work) and I'
egonw <[EMAIL PROTECTED]> writes:
> Ok, in addition to the current Debian policy, a third, preferred
> option, being the gcj compiled library.
Yes. The interpreter (VM) that is part of the gcj run-time library
allows you to include a .so in the classpath, and it is searched for
needed classes ju
On 03 Apr 2001 07:50:33 +0200, Egon Willighagen wrote:
> > I've left out versioning issues. If one want to support multiple
> > versions of the same library one could install LIBRARY-VERSION.jar,
> > and install a symlink from LIBRARY.jar, but having compilers and
> > VMs pick the right version is
[EMAIL PROTECTED] (Andrew Pimlott) writes:
> > JNI libraries shold probably (by default) go in either /usr/lib
> > or /usr/lib/java. The latter again has the advantage of reducing
> > clutter and name clashes, but I don't know how awkward that would
> > be for other Java implementations.
>
> Ok
[EMAIL PROTECTED] (Andrew Pimlott) writes:
> What recommendation should we make to packagers of libraries that
> have native components? I assume that Java native method APIs (like
> JNI) are source-level, not binary-level.
JNI is binary-level, in the sense that compiled JNI code should
be indep
Ok, it looks like my understanding of the details is lacking. I'll
try to keep this message on a higher level. Sorry for any
confusion.
On Tue, Apr 03, 2001 at 08:58:19AM -0700, Per Bothner wrote:
> [EMAIL PROTECTED] (Andrew Pimlott) writes:
> > On the other hand, if JNI is an ABI, it would
> >
On Tue, Apr 03, 2001 at 06:47:37AM -0400, egonw wrote:
> Indeed. But the principle holds that in Debian, with dependencies, that
> a certain executable exactly knows where to find a certain library.
Not true. Executables declare dependencies on soname's. It is the
job of the runtime linker to de
egonw <[EMAIL PROTECTED]> writes:
> Ok, in addition to the current Debian policy, a third, preferred
> option, being the gcj compiled library.
Yes. The interpreter (VM) that is part of the gcj run-time library
allows you to include a .so in the classpath, and it is searched for
needed classes j
On 03 Apr 2001 07:50:33 +0200, Egon Willighagen wrote:
> > I've left out versioning issues. If one want to support multiple
> > versions of the same library one could install LIBRARY-VERSION.jar,
> > and install a symlink from LIBRARY.jar, but having compilers and
> > VMs pick the right version i
My background in these issues is modest, but I have a strong
interest in seeing them resolved, so let me try to add something.
On Mon, Apr 02, 2001 at 05:43:55PM -0700, Per Bothner wrote:
> So where should be put the .jar files? I suggest leaving this as
> /usr/share/java. However, we should add
[EMAIL PROTECTED] (Andrew Pimlott) writes:
> What recommendation should we make to packagers of libraries that
> have native components? I assume that Java native method APIs (like
> JNI) are source-level, not binary-level.
JNI is binary-level, in the sense that compiled JNI code should
be inde
On Tue, Apr 03, 2001 at 06:47:37AM -0400, egonw wrote:
> Indeed. But the principle holds that in Debian, with dependencies, that
> a certain executable exactly knows where to find a certain library.
Not true. Executables declare dependencies on soname's. It is the
job of the runtime linker to d
My background in these issues is modest, but I have a strong
interest in seeing them resolved, so let me try to add something.
On Mon, Apr 02, 2001 at 05:43:55PM -0700, Per Bothner wrote:
> So where should be put the .jar files? I suggest leaving this as
> /usr/share/java. However, we should ad
Quoting Per Bothner <[EMAIL PROTECTED]>:
> > Op dinsdag 03 april 2001 02:43, schreef Per Bothner:
> > > I'd like to make some progress on standard Linux/GNU installation
> > > standards for Java, and how GCJ fits into this.
> >
> > Have you taken over the maintainership? (Just wondering)
>
> I
Quoting Seth Arnold <[EMAIL PROTECTED]>:
> > > With this setup:
> > > (1) All Java compilers and VMs can compile find all "installed"
.jars,
> > > without users having to fiddle with classpaths.
>
> I do not like this idea.
I agree. I mentioned it because it came up in earlier discussions.
> Ther
Quoting Per Bothner <[EMAIL PROTECTED]>:
> > Op dinsdag 03 april 2001 02:43, schreef Per Bothner:
> > > I'd like to make some progress on standard Linux/GNU installation
> > > standards for Java, and how GCJ fits into this.
> >
> > Have you taken over the maintainership? (Just wondering)
>
> I
* Per Bothner <[EMAIL PROTECTED]> [010403 00:01]:
> Well, I'm not focusing on Debian - I'm actually currently using Red Hat.
Aha; I assumed you used Debian because you have posted in debian-java
before, over the course of several months IIRC.
I imagine that most any improvements in handling Java
Quoting Seth Arnold <[EMAIL PROTECTED]>:
> > > With this setup:
> > > (1) All Java compilers and VMs can compile find all "installed"
.jars,
> > > without users having to fiddle with classpaths.
>
> I do not like this idea.
I agree. I mentioned it because it came up in earlier discussions.
> The
Seth Arnold <[EMAIL PROTECTED]> writes:
> (Per, glad to see you are interested in making Java as cool in Debian
> as native stuff is handled currently. :)
Well, I'm not focusing on Debian - I'm actually currently using Red Hat.
My goal is to make Java cool in GNU generally, and GNU/Linux specific
* Egon Willighagen <[EMAIL PROTECTED]> [010402 22:58]:
> Op dinsdag 03 april 2001 02:43, schreef Per Bothner:
> > I'd like to make some progress on standard Linux/GNU installation
> > standards for Java, and how GCJ fits into this.
(Per, glad to see you are interested in making Java as cool in Deb
Egon Willighagen <[EMAIL PROTECTED]> writes:
> Op dinsdag 03 april 2001 02:43, schreef Per Bothner:
> > I'd like to make some progress on standard Linux/GNU installation
> > standards for Java, and how GCJ fits into this.
>
> Have you taken over the maintainership? (Just wondering)
I hope no
Op dinsdag 03 april 2001 02:43, schreef Per Bothner:
> I'd like to make some progress on standard Linux/GNU installation
> standards for Java, and how GCJ fits into this.
Have you taken over the maintainership? (Just wondering)
> This could lead to an updated Debian Java policy (which is
> at
* Per Bothner <[EMAIL PROTECTED]> [010403 00:01]:
> Well, I'm not focusing on Debian - I'm actually currently using Red Hat.
Aha; I assumed you used Debian because you have posted in debian-java
before, over the course of several months IIRC.
I imagine that most any improvements in handling Java
30 matches
Mail list logo
