From: Troy Dack <troy@tkdack.com>
To: Riyad Kalla <rsk@u.arizona.edu>
Cc: 'Christian cycloon Gut' <cycloon@is-root.org>, gentoo-dev@gentoo.org
Subject: RE: [gentoo-dev] gtk+-2.2.0 & eclipse
Date: 16 Jan 2003 00:11:34 +1100 [thread overview]
Message-ID: <1042636293.2923.4.camel@waterhouse.internal.lan> (raw)
In-Reply-To: <001801c2b82b$18972ba0$d628c480@rsk>
On Fri, 2003-01-10 at 09:04, Riyad Kalla wrote:
> I'm just gonna ask, cause I don't understand this.
>
> When people refer to the emerging of Java, are you talking about
> downloading the source separately via a SCSL agreement, and then running
> emerge which compiles it, OR does emerge actually download the sun's
> binary distribution of it, helping me to avoid treking over to
> java.sun.com to download it myself?
>
> The binary-only nature of the JDK is what confuses me when used in an
> "emerge" context.
>
> Thanks for any clarification!
In this case you can do either. There are ebuilds that fetch the binary
.tar.gz's and imstall them.
There are also ebuilds that instruct you to go to sun, read the
agreement, download the sources, place them in /usr/portage/distfiles
and then re-run the ebuild to actually compile java from source.
The second method does still require a binary java installed to perform
the actual biuld of java from source though. Once you have your own
java built you can safely unmerge the other binary java package(s).
--
Troy Dack
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-01-15 13:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 17:42 [gentoo-dev] gtk+-2.2.0 & eclipse Mike Hogye
2003-01-09 21:04 ` Christian cycloon Gut
2003-01-09 22:04 ` Riyad Kalla
2003-01-15 13:11 ` Troy Dack [this message]
2003-01-09 23:02 ` Jan Winhuysen
2003-01-10 0:00 ` Matthew Kennedy
2003-01-10 1:14 ` foser
2003-01-10 8:36 ` Matthew Kennedy
2003-01-10 13:24 ` foser
2003-01-10 13:45 ` Mike Hogye
2003-01-10 15:58 ` foser
2003-01-10 16:16 ` Jan Winhuysen
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=1042636293.2923.4.camel@waterhouse.internal.lan \
--to=troy@tkdack.com \
--cc=cycloon@is-root.org \
--cc=gentoo-dev@gentoo.org \
--cc=rsk@u.arizona.edu \
/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