public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William L. Thomson Jr." <wlt@obsidian-studios.com>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Netbeans
Date: Sat, 08 Jul 2006 17:23:32 -0400	[thread overview]
Message-ID: <1152393812.15032.9.camel@wlt.obsidian-studios.com> (raw)
In-Reply-To: <4e2f58480607081412l5d0db64axb2ae4439673b4c14@mail.gmail.com>

On Sat, 2006-07-08 at 17:12 -0400, nil nil wrote:
> That makes sense. I mean that, I understand the gentoo philosophy
> concerning source code, however, I don't think it really applies to
> java code. Java byte code is supposed to compile the same everywhere.

It has more to do with philosophy, layout, using the latest deps that
are normally bundled to build any given app. Not so much compile time
tweaks, optimizations or the other stuff one can do with say C or C++
during compilation.

For example diff of compiling an app say with it's bundled log4j v1.2.11
or using the current 1.2.13.

>  There are very few javac options which will affect the bytecode
> coming out. If compilation to native code is needed, gcj et al. can
> handle compiling bytecode. Point being, there's no benefit to
> compiling from java source (except to native), and if the distributers
> will compile it for you it only saves cpu cycles. 

Java code compiles so fast it's a moot issue. Even something as big as
Netbeans on slower hardware almost takes more time to unpack than to
compile.

> The second thing with distributers packing their own jars in I
> understand. I can only say that if it does waste memory to have extra
> jars lying around, it's still better to have that and the application
> than no application at all. At least in my book. A solution could be
> worked out later to put the jars in their own ebuilds. 

Been there done that. Which is why these days any new ebuilds MUST not
use any bundled jars. If they are not in their own packages, that has to
occur before the ebuild. Such is life.

The previous state there was a mixture of binaries, most all with their
own bundled deps. Even if that is already present on the system. It made
a mess, took a while to clean up, and pretty sure those in charge are
really against going back down that road. I don't blame them.

> The third thing, and I mention it now to make up for being perhaps
> overly critical of a process I know very little about, is why I joined
> this list in the first place. I'd like to help the gentoo-java
> project. I don't know much about how to help, though, so if anyone
> could point me in the right direction I'll come back later in a better
> position to help. 

Hit up IRC #gentoo-java @ freenode.net most all of the active players
tend to lurk there at some point or another. Bug squashing or reporting
is always welcome. Testing experimental packages providing feedback etc
is all greatly appreciated.

If you want to do more than that, ebuild contributions are welcome,
patches to improve existing ones. For those with allot of time, or the
motivation. We surely could use more Gentoo Java Developers, which I am
in the process of becoming one. Bit of work and time commitment to get
to that point.

-- 
Sincerely,
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com

-- 
gentoo-java@gentoo.org mailing list



      reply	other threads:[~2006-07-08 21:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08  1:29 [gentoo-java] Netbeans nil nil
2006-07-08  2:16 ` William L. Thomson Jr.
2006-07-08  9:40   ` Wiktor Wandachowicz
2006-07-08 21:12     ` nil nil
2006-07-08 21:23       ` William L. Thomson Jr. [this message]

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=1152393812.15032.9.camel@wlt.obsidian-studios.com \
    --to=wlt@obsidian-studios.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