Date: Mon, 19 Jun 2006 23:24:17 +0200 From: Alex Dupre <ale@FreeBSD.org> To: Greg Lewis <glewis@eyesbeyond.com> Cc: freebsd-java@FreeBSD.org Subject: Re: Java crypto Message-ID: <44971601.3070902@FreeBSD.org> In-Reply-To: <20060619195745.GA29915@misty.eyesbeyond.com> References: <449011B4.9060502@FreeBSD.org> <20060619195745.GA29915@misty.eyesbeyond.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg Lewis ha scritto: > Thanks for asking about this. Upon taking a quick look, I don't think > there is any particular reason. My guess is that simply noone noticed we > weren't building it. This isn't surprising given that it looks to me > like its not built on Solaris/Linux/Windows either, its simply extracted > from a zip file. It also looks like the source code is also zipped up, > which makes it harder to notice its even there. Yes, I supposed it. The jar file cannot be built from sources, since must be signed, so I think Sun chose to distribute even the jni shared object in binary form for "supported" platforms. The source distribution doesn't automatically build it, but native binary distributions install it and it's supposed to be in jdk 1.5. I don't know which is the best way to go, but probably the easiest is to create a new port that builds the jni lib and installs it along with the signed jar (I think modifying the jdk15 and diablo ports will be more complex, even if more natural from a user's point of view). >> Second thing: it could be useful to have a knob in all jdk ports to >> install the unrestricted security policy files, so that every update >> won't replace them. > > I'd be happy to review patches :). I will prepare them asap. -- Alex Dupre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44971601.3070902>