One simple fact, the ebuilds don't rely on the rpms, they use the
self-extracting binaries distributed by Sun. Check the ebuild for
1.5.0.03:
x86file="jdk-${MY_PVA}-linux-i586.bin"
Sun distributes their JDK and JRE in two formats, the broken RPM you
mentioned, and a generic self extracting/installing archive. The
portage ebuild uses the latter, extracts into the portage build
environment, and then copies into the actual system. Yum might not
have the flexibility to deal with this .bin file, seeing as it's based
on RPM, though there's nothing stopping people from making personal
RPMs from the .bin file after extracting it, but distributing it on
the Internet would likely get Sun banging on your door as they want
you to go through their license agreement before downloading.
On 5/22/05, THUFIR HAWAT <[EMAIL PROTECTED]> wrote:
> On 5/23/05, Mark Shields <[EMAIL PROTECTED]> wrote:
> ...
> > I can't give you a factual answer, but I can give you a guess: it's
> > possible yum has different guidelines on including files, such as
> > the sun-jdk you pointed out. Licensing restrictions, maybe? But
> > no, that wouldn't make sense. Or would it?
> ...
>
> there is sun/rpm bug at
> <http://bugs.sun.com/bugdatabase/view_bug.do;:YfiG?bug_id=4680244>,
> and I'm sure there're more. Thanks to Nick Rout pointing out that yum
> is a front end for rpm, I'll clarify my question:
>
> due to that bug, which I probably should've mentioned in my first
> post, a JDK RPM doesn't exist (outside of JPackage). What is emerge
> doing which allows it to bypass this bug? if my facts are in error,
> please correct them.
>
>
> thanks,
>
> Thufir
>
> --
> gentoo-user@gentoo.org mailing list
>
>
--
gentoo-user@gentoo.org mailing list
