JRE install bundles for 6u10 are non-executable
Kelly.Ohair at Sun.COM
Wed Jul 30 10:42:21 PDT 2008
Martin Buchholz wrote:
> Andrew raises a good point.
> It's true that Sun does not provide binaries for OpenJDK,
> and the code that deploys them is not open source,
> but... it would be nice if Sun did provide OpenJDK binaries
> (since Sun builds them)
OpenJDK is an open source delivery, the JDK7 builds are built
from the OpenJDK7 sources plus more.
The JDK7 has specific build platforms we build on, some of which
may not be the build platforms that make sense for various users
of the OpenJDK. We will be upgrading but that takes time.
We test build just the OpenJDK (+binaryplugs) on select systems,
but there are no bundles and these builds are very limited as
to where they could be run.
If an open source developer needs a pure OpenJDK build for a
particular platform/compiler, the basic concept is that they
would build it themselves.
The list of possible build platforms and compiler combinations
is just too long to make any other approach make sense right now.
> and I would certainly expect the web deployment code
> to become open source eventually, even if not technically
> a part of OpenJDK.
Can't speak to that issue.
> If I were still at Sun, I probably would have used
> Sun's internal bug-tracking system to report such bugs.
The bug with the execute permissions is filed, are you refering
to another bug?
And P1 is a priority given to bugs that have no workaround, having
to 'chmod a+x bin/* jre/bin/*' after installing a tarball, doesn't
seem like so bad a workaround.
I agree this is a problem that should be fixed, but if we made all
bugs like this P1, well.. just doesn't make sense.
> On Wed, Jul 30, 2008 at 4:13 AM, Andrew John Hughes
> <gnu_andrew at member.fsf.org> wrote:
>> 2008/7/30 Martin Buchholz <martinrb at google.com>:
>>> I installed the Linux JREs for 6u10 b28,
>>> (using java -jar jre......jar)
>>> and was surprised to discover none of the
>>> programs (like "bin/java") were executable.
>>> I checked earlier 6u10 builds,
>>> and they have the same problem.
>>> I suspect the jdk7 builds also have this problem.
>>> This seems like a P1 deployment bug.
>>> Hasn't anyone ever run sanity checks
>>> on JREs installed this way?
>> How is this related to OpenJDK?
>> Andrew :-)
>> Support Free Java!
>> Contribute to GNU Classpath and the OpenJDK
>> PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
>> Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
More information about the build-dev