From: "Alon Bar-Lev" <alon.barlev@gmail.com>
To: "Andrew John Hughes" <gnu_andrew@member.fsf.org>
Cc: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] icedtea6 bootstrap
Date: Mon, 15 Sep 2008 08:08:08 +0300 [thread overview]
Message-ID: <9e0cf0bf0809142208g2140ffc4kc205e0e069e58884@mail.gmail.com> (raw)
In-Reply-To: <9e0cf0bf0809142112w70b06774l539cbce4940d30cc@mail.gmail.com>
On 9/15/08, Alon Bar-Lev <alon.barlev@gmail.com> wrote:
> > Well this is probably a flaw in portage then, but the solution is only
> > a two-step emerge process:
> >
> > emerge gcj-jdk
> > emerge icedtea6
> >
> > I don't think that's inherently difficult.
>
>
> You forgot:
> java-config -S icedtea6
> emerge --unmerge gcj-jdk
And on a second thought... You need also add the gcj USE flag to gcc,
reemerge gcc, then at the end remove the gcj USE flag from gcc and
reemerge gcc.
So it is much more complex.
So basically, provided that >=gcc-4.3 is stable, this is the outline
of what I thought, you can make it more efficient if you check for
other valid jdks and not force only gcj...
if installed icedtea6; then
exit 0
fi
if ! has_use gcc gcj; then
should_remove_gcj_use_from_gcc=1
USE="gcj" emerge --oneshot gcc || die
fi
if ! installed gcj-jdk; then
should_remove_gcj_jdk=1
emerge --oneshot gcj-jdk || die
fi
old_java=$(java-config -f)
java-config -S gcj-jdk || die
emerge icedtea6 || die
if [ ${old_java}" = "gcj-jdk" -a -n "${should_remove_gcj_jdk}" ]; then
java-config -S icedtea6 || die
else
java-config -S $(old_java) || die
fi
[ -n "${should_remove_gcj_jdk}" ] && emerge --unmerge gcj-jdk
[ -n "${should_remove_gcj_use_from_gcc}" ] && emerge --oneshot gcc
exit 0
next prev parent reply other threads:[~2008-09-15 5:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-14 12:38 [gentoo-java] icedtea6 bootstrap Alon Bar-Lev
2008-09-14 20:38 ` Andrew John Hughes
2008-09-15 4:12 ` Alon Bar-Lev
2008-09-15 5:08 ` Alon Bar-Lev [this message]
2008-09-16 23:44 ` Andrew Cowie
2008-09-17 17:40 ` Andrew John Hughes
2008-09-17 18:19 ` Alon Bar-Lev
2008-09-17 22:01 ` Andrew John Hughes
2008-09-16 8:58 ` Andrew John Hughes
2008-09-15 11:35 ` Philipp Riegger
2008-09-15 11:42 ` Philipp Riegger
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=9e0cf0bf0809142208g2140ffc4kc205e0e069e58884@mail.gmail.com \
--to=alon.barlev@gmail.com \
--cc=gentoo-java@lists.gentoo.org \
--cc=gnu_andrew@member.fsf.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