I have been receiving quite a bit of irritation from the Debian-Java
lists lately so I thought I would try and address the issues.
Here is the situation:
- The production version of Kaffe is 1.0b4. I packaged it the day that
it was released. I have made a subsequent packaging of 1.0b4 to
eli
(debian-devel stuff halfway down**)
> From: Stephane Bortzmeyer <[EMAIL PROTECTED]>
> Jikes has a problem with core classes. It can use those of the JDK or those
> of
> kaffe (which allows it to stay free) but is is necessary to tell it where to
> find them.
>
> ...
> Which means you canno
If there is no work currently being done to package Cocoon (a XML/XSL
publishing framework servlet, http://java.apache.org/cocoon) and its direct
dependencies (OpenXML, http://www.openxml.org and XSL:P,
http://www.clc-marketing.com/xslp/), I'd like to provide these packages. As I'm
not current
Make a file "/usr/share/java/core-compiler-classes.jar" that is managed
via the alternatives mechanism. Some other name could be used, but this
would suffice. There could be a virtual package of the same name which
is provided by the debs which supply said .jar.
On another note, I think that this
On Wednesday 8 September 1999, at 15 h 35, the keyboard of "Mike Goldman"
<[EMAIL PROTECTED]> wrote:
> Just FWIW, I do configure Jikes for Debian to automatically find clases in
> the Java Repository. So if you manually unpack core classes into
> /usr/share/java/repository, Jikes will presently
On Wednesday 8 September 1999, at 21 h 8, the keyboard of "Ean R . Schuessler"
<[EMAIL PROTECTED]> wrote:
> Despite this, Mike
> Goldman has decided to make out that I have "orphaned" Kaffe.
The assumption was certainly false, but anyone can have doubts
when reading the bug list of kaffe. O
On Thu, Sep 09, 1999 at 10:28:30AM +0200, Stephane Bortzmeyer wrote:
> My name is Stéphane. You can drop the accent on the first e if it
> is more convenient.
Apologies.
> Thanks for the "half conceived". The proposed Java policy has been
> sent on this list several months ago and discussed and
On Thursday 9 September 1999, at 0 h 16, the keyboard of Daniel Barclay
<[EMAIL PROTECTED]> wrote:
> Most of Unix is based on configuring or controlling things with
> environment variables. Things (e.g., Sun's JVM) are designed with
> that in mind. When there aren't appropriate defaults befor
Ean, Staphane... I think I understand how each of you two feel; however,
I would like to remind you guys that this whole thing is supposed to be
fun. :) This is sort of degenerating into a bit of a flame war; perhaps
before responding to future messages (including this one? :) take a few
minutes t
I agree with Seth on this matter, but I wish to point out that according
to the GPL that you both have the right to take a body of code [with the
original authors express permission] and incorporate it into a compleate
new body of work, with a new name. In short, if you can't agree to work
together
Mark W. Eichin writes:
> [goes back to lurking until free-java is good enough to consider as an
> *only* java environment :-)]
Yeah. It's not only that we'd need an LGPL'ed VM and core
classes, and a GPL'ed compiler. I tried to make this point
last year that we would need some kind of experiment
Bernd Kreimeier Writes:
> When we can implement find etc. in pure Java, and create
> ELF as well as a bytecode from the same Java source using
> free tools, when we can execute nfind and jfind as quickly
> and efficiently as /usr/bin/find, when Find.java uses
> a FindOperator class that can be use
Daniel James Patterson Writes:
> I believe that perl has the ability to generate C code from perl scripts,
> which you can then compile yourself. As far as i can remember, it was
> a new feature for perl 5.004 when it arrived. I think it's mentioned
> somewhere in the perl man pages, but I'm not
13 matches
Mail list logo
