From owner-freebsd-java@FreeBSD.ORG Tue Sep 26 18:33:29 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 0E8EA16A40F; Tue, 26 Sep 2006 18:33:29 +0000 (UTC) (envelope-from dsledge@appriss.com) Received: from intexch02.int.appriss.com (intexch02.int.appriss.com [63.126.72.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id A49A443D49; Tue, 26 Sep 2006 18:33:08 +0000 (GMT) (envelope-from dsledge@appriss.com) Received: from [10.11.3.10] ([10.11.3.10]) by intexch02.int.appriss.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Sep 2006 14:33:07 -0400 Message-ID: <45197263.50505@appriss.com> Date: Tue, 26 Sep 2006 14:33:07 -0400 From: David Sledge User-Agent: Thunderbird 1.5.0.7 (X11/20060915) To: Sergey Matveychuk References: <4518BED7.3050104@FreeBSD.org> In-Reply-To: <4518BED7.3050104@FreeBSD.org> Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 Sep 2006 18:33:07.0807 (UTC) FILETIME=[3640D6F0:01C6E19A] MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-java@freebsd.org" , Ronald Klop Subject: Re: Will eclipse32 be committed before ports freeze? (pr ports/102993) 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: Tue, 26 Sep 2006 18:33:29 -0000 Sergey Matveychuk wrote: Ronald Klop wrote: Hello, 10 October is the ports freeze for FreeBSD 6.2. Will the port of Eclipse 3.2 be committed before then? It is a new port, so I don't think it will interrupt with other ports. 1) We need a repocopy. On the feedback for the PR I answered that I did not think a repocopy was needed since almost all of the files are new with different names for the eclipse32 port. I only kept a handful of the original files. If the person who is going to do the commit prefers to due a repocopy anyways thats fine and I will make a patch file to replace the shar file already there. I just need to know what the committer needs. I have not received any updates for the PR other than the request for feedback that I responded to. 2) We need a patch against an old version after that. If a repocopy is not required then the shar file should be sufficient.