public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Cowie <andrew@operationaldynamics.com>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] work on gcj for gentoo
Date: Wed, 22 Feb 2006 19:16:22 +1100	[thread overview]
Message-ID: <1140596182.19188.15.camel@procyon.operationaldynamics.com> (raw)
In-Reply-To: <43FB35B6.10105@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]

On Tue, 2006-02-21 at 10:45 -0500, Joshua Nichols wrote:
> I'm not fond of the name gcj-jdk. The ebuild Andrew made was just for 
> gcj itself, without the Java compatibility stuff, iirc. -jdk suggests 
> that it provides a usable JDK, which it doesn't as it was.

... but was hoping to get there some day.

> Speaking of which, I think the added compatibility layer (for javac, 
> java, etc) should be a separate package. I'm not sure if this was your 
> intention or not. Either way, it would make sense, since you would most 
> likely be able to use the same layer for different versions of gcj.

You guys are the devs, so packag{ing,e name} decisions are yours to make
as you see fit.

The decision would seem to be

        dev-java/gcj
        dev-java/java-gcj-compat depends on dev-java/gcj

vs

        dev-java/gcj-jdk

While I prefer the latter name, I am very sensitive to the issue that
once we call it a jdk (or rather, once java-config allows it to be
selected) we're in for a nightmare of people's expectations not matching
what is actually there...

[shit like "why isn't it magically creating a binary for me? I thought
GCJ created binaries! Bastards, rant rant rant]

... which we'll probably get either way, especially as people
misunderstand the { dev-java/gnu-classpath version vs gcj's imported
version of classpath } issue and the { what Free Java is capable of
these days } issue and the { gcj -C plus gij as JDK vs gcj -c plus gcj
(link) as native compiler } issue.

Lots of misunderstanding! Oh well. Doesn't mean we shouldn't carry on
and leverage what the Red Hat boys are up to.

AfC
Sydney


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-02-22  8:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 15:04 [gentoo-java] work on gcj for gentoo Hanno Meyer-Thurow
2006-02-21 15:42 ` Karl Trygve Kalleberg
2006-02-21 18:14   ` Hanno Meyer-Thurow
2006-02-21 18:21     ` Karl Trygve Kalleberg
2006-02-21 15:45 ` Joshua Nichols
2006-02-21 15:55   ` Joshua Nichols
2006-02-21 17:53   ` Hanno Meyer-Thurow
2006-02-22  8:16   ` Andrew Cowie [this message]
2006-02-27 22:38     ` Hanno Meyer-Thurow
2006-03-01 12:30       ` Andrew Cowie
2006-03-01 14:38         ` Hanno Meyer-Thurow
2006-02-28  7:34     ` [RESEND] " Hanno Meyer-Thurow
2006-02-22 16:51 ` Hanno Meyer-Thurow
2006-02-23  2:09 ` Andrew Cowie
2006-02-23 11:25   ` Hanno Meyer-Thurow
2006-02-24 17:26     ` Hanno Meyer-Thurow
2006-02-25 14:43       ` Hanno Meyer-Thurow
2006-02-28 10:25 ` Hanno Meyer-Thurow
2006-02-28 20:37   ` Hanno Meyer-Thurow
2006-03-02 10:35   ` Hanno Meyer-Thurow
2006-03-11 20:51 ` Hanno Meyer-Thurow
2006-03-12 18:25   ` Hanno Meyer-Thurow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1140596182.19188.15.camel@procyon.operationaldynamics.com \
    --to=andrew@operationaldynamics.com \
    --cc=gentoo-java@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox