From owner-freebsd-java@FreeBSD.ORG Mon Jun 19 21:24:27 2006 Return-Path: X-Original-To: freebsd-java@FreeBSD.org Delivered-To: freebsd-java@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A712E16A47B for ; Mon, 19 Jun 2006 21:24:27 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from andxor.it (relay.andxor.it [195.223.2.3]) by mx1.FreeBSD.org (Postfix) with SMTP id A2D9743D45 for ; Mon, 19 Jun 2006 21:24:25 +0000 (GMT) (envelope-from ale@FreeBSD.org) Received: (qmail 49321 invoked from network); 19 Jun 2006 21:24:18 -0000 Received: from unknown (HELO ?192.168.178.2?) (a.premoli@andxor.it@81.174.31.42) by andxor.it with SMTP; 19 Jun 2006 21:24:18 -0000 Message-ID: <44971601.3070902@FreeBSD.org> Date: Mon, 19 Jun 2006 23:24:17 +0200 From: Alex Dupre User-Agent: Mozilla Thunderbird 1.5.0.4 (X11/20060605) MIME-Version: 1.0 To: Greg Lewis References: <449011B4.9060502@FreeBSD.org> <20060619195745.GA29915@misty.eyesbeyond.com> In-Reply-To: <20060619195745.GA29915@misty.eyesbeyond.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-java@FreeBSD.org Subject: Re: Java crypto X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2006 21:24:27 -0000 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