From owner-freebsd-java@FreeBSD.ORG Wed Nov 21 05:21:38 2007 Return-Path: Delivered-To: java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B29D16A468 for ; Wed, 21 Nov 2007 05:21:38 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.freebsd.org (Postfix) with ESMTP id 01B1913C47E for ; Wed, 21 Nov 2007 05:21:37 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.14.1/8.14.1) with ESMTP id lAL5LbaN001238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 21 Nov 2007 00:21:37 -0500 (EST) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.14.1/8.14.1/Submit) id lAL5LaPh001237 for java@freebsd.org; Wed, 21 Nov 2007 00:21:36 -0500 (EST) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: java@freebsd.org Date: Wed, 21 Nov 2007 00:21:36 -0500 User-Agent: KMail/1.9.6 MIME-Version: 1.0 X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: jdk15..._14 update 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: Wed, 21 Nov 2007 05:21:38 -0000 --Boundary-00=_gB8QHJoDDRw5kt5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello! The attached patches both update the JDK to the recently released patch-level 14. They also both modify the extraction algorithm to make it more reliable -- it currently hard-codes the line-number, where the data begins -- the number needs to change every time the JDK changes. The first method simply looks for the line "^exit 0", which is a more reliable indicator of the end of the shell-script, than a hard-coded line number. I like the second method even better, though, because it avoids running a Linux program at extract time (using a native unzip instead) and is, likely, even more reliable, than relying on "^exit 0" being in the right place. Whichever method you chose, future updates to the port should consist of simply bumping the JDK patch-level... Yours, -mi --Boundary-00=_gB8QHJoDDRw5kt5--