public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Riyad Kalla" <rsk@u.arizona.edu>
To: <absinthe@gentoo.org>, <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] JRE support - is it worth it?
Date: Tue, 20 May 2003 09:40:08 -0700	[thread overview]
Message-ID: <000501c31eee$79308ae0$d628c480@rskwork> (raw)
In-Reply-To: <200305192349.32237.absinthe@gentoo.org>

I agree with your reasoning. I support the cutting of the JRE (actually
I don't think I've downloaded the JRE since 1.2)

-Riyad

-----Original Message-----
From: Dylan Carlson [mailto:absinthe@gentoo.org] 
Sent: Monday, May 19, 2003 8:49 PM
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] JRE support - is it worth it?


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,

This is not an RFC, per se, but I am posting this with the general
purpose of soliciting discussion.  This might be a controversial
subject, so I think it warrants some conversation before it reaches the
level of an RFC.

I have talked with a couple of people the idea of dropping JRE support
in Gentoo.  The reasons this idea came about:

1.  Gentoo is a source-based distribution.  We have Java-based packages
that build from source for the same reason that have C packages that
build from source.  Yet, it's unthinkable to have a system without a C
compiler. Thus it should be almost as unthinkable to have a system
without a Java compiler.

2.  Few people actually use a JRE inside of Gentoo for the above reason
(if
any) ... yet of course reliable statistics on this are not available.
Furthermore, some packages require a JDK to run, namely servlet engines,
development environments, and rare apps that depend on the JDK without
actually compiling/debugging anything.

3.  Jikes will compile most things, but not everything.  Furthermore,
Jikes lacks a javadoc tool, among other things.  So it's not suitable to
have a JRE + Jikes combination, though in theory that might be possible
someday.


User impact to the above idea:

1.  Download & install size:   Using 1.4 as our example, JRE's are about
a
22MB download.  JDKs are about 42MB.   It's also safe to assume that the
JDKs also occupy roughly twice the disk space, though I don't have
specifics on it for this email.

2.  Reduced complexity in java-config(1), simplifies the nature of Java
ebuilds for both Gentoo developers and users submitting ebuilds alike.

3.  Reduced QA burden.

I would like to hear your thoughts on this.

Cheers,
Dylan Carlson

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
Key fingerprint = 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+yaXKPQS8wXCOFl8RAg/IAJ9s7FL6mRrciaCMU3med2CGUysRZgCcDvlB
fj/MRBGYX0e8mjjs2fDisG4=
=hpnd
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-05-20 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20  3:49 [gentoo-dev] JRE support - is it worth it? Dylan Carlson
2003-05-20 16:32 ` Chris Davies
2003-05-20 18:22   ` Todd Berman
2003-05-20 22:41   ` Dylan Carlson
2003-05-20 23:47     ` William Kenworthy
2003-05-21  0:56     ` Chris Davies
2003-05-20 16:40 ` Riyad Kalla [this message]
2003-05-20 18:01 ` Brad Laue
2003-05-20 21:57 ` George Shapovalov
2003-05-21  9:48 ` [gentoo-dev] " Stephan Feder

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='000501c31eee$79308ae0$d628c480@rskwork' \
    --to=rsk@u.arizona.edu \
    --cc=absinthe@gentoo.org \
    --cc=gentoo-dev@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