http://beboy66.info/p3/?id=lgherbs
s0denudation
Jerry Haltom <[EMAIL PROTECTED]> writes:
> Curiously,
>
> Can building these .class files built with Kaffee prevent their usage
> with a non-free alternative JVM? If Kaffe is totally Java standards
> compliant, then that's cool... is that the case? Will there be ANY
> deficiencies in these classes
Etienne Gagnon <[EMAIL PROTECTED]> writes:
> Daniel Bonniot wrote:
>> Etienne Gagnon wrote:
>>> The biggest problem is that Kaffe is licensed under the GNU GPL, so
>>> if an application/library can only be compiled with Kaffe, it must
>>> be licensed under the GPL too (or at least be "license comp
Hello Etienne,
I repeat: I am simply pointing you to the relevant documentation,
Thanks for the pointers. I am aware of those discussions, having
followed some of them on this list.
but I
am not
willing to discuss the issue.
I don't want to restart that discussion either ;-)
I was asking yo
Daniel Bonniot wrote:
The biggest problem is that Kaffe is licensed under the GNU GPL, so if an
application/library can only be compiled with Kaffe, it must be licensed
under the GPL too (or at least be "license compatible" with the GPL).
Given that this case seldom/never happens, I wouldn't say t
Etienne Gagnon wrote:
In other words, I would be very wary of a GPL incompatible package that
has a "build-depends" on kaffe only, or a depends on kaffe only. (adding
a non-working build-depends or depends does not count).
I should illustrate this:
$ apt-cache showsrc junit
...
Build-Depends-Inde
Salut Daniel, Etienne,
Daniel Bonniot wrote:
I was asking you a yes or no question about what you meant in your
message: you agree the GPL would only apply to programs that can run
only with Kaffe, and cannot run with, say, Sun's JVM? Looking at the
message you linked to, I would assume yes, b
If a debian package can only be built using Kaffe, then it depends on Kaffe
and thus should be GPL compatible, according to both the debian-legal
concensus
and the FSF interpretation. Unless I am missing something?
I think you are mixing the debian package with the upstream program.
Upstream pro
Dalibor Topic wrote:
It's an interesting question whether compilation with a GPL'd program
causes the output to be GPLd. I don't see an FAQ entry on the FSF page
for that, so I'd propose to take the discussion to debian-legal, if
necessary.
Let me clarify.
It's not compilation using a GPL progr
Dis+count Ph.armacy Onlin,e
Sa^ve up t\o %8O orde!ring your meds online
No presc*ription required
fast disc!reet s/hipping, ov|ernight nextday air
FDA & Do,ctor Ap]proved
Xan\ax - Cia]lis - Via_gra - Vali`um
Pl`ace Your Or}der Here Tod~ay
no moore
distinct laurentian workspace ce
Daniel Bonniot <[EMAIL PROTECTED]> writes:
> I think you are mixing the debian package with the upstream program.
And remember that a build-depends is really a suggestion. The end user
can override it and build the package with Sun JDK, for example.
--
* Sufficiently advanced magic is indistingu
11 matches
Mail list logo
