From owner-freebsd-java@FreeBSD.ORG Tue Aug 29 21:12:46 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 1302C16A4DA for ; Tue, 29 Aug 2006 21:12:46 +0000 (UTC) (envelope-from jbq@caraldi.com) Received: from caraldi.com (195-13-58-165.oxyd.net [195.13.58.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7628243D70 for ; Tue, 29 Aug 2006 21:12:43 +0000 (GMT) (envelope-from jbq@caraldi.com) Received: from watt.caraldi.com (laf31-2-82-224-106-41.fbx.proxad.net [82.224.106.41]) by caraldi.com (Postfix) with ESMTP id E865B60E1 for ; Tue, 29 Aug 2006 23:12:35 +0200 (CEST) Received: by watt.caraldi.com (Postfix, from userid 1001) id 30656223; Tue, 29 Aug 2006 23:12:35 +0200 (CEST) Date: Tue, 29 Aug 2006 23:12:35 +0200 From: Jean-Baptiste Quenot To: freebsd-java@freebsd.org Message-ID: <20060829211234.GB1229@watt.intra.caraldi.com> Mail-Followup-To: freebsd-java@freebsd.org References: <970c0a6b0607280839qc05e2b8p51118955745b7cda@mail.gmail.com> <20060828161538.GI89053@vision.anyware> <44F332FF.5050809@appriss.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <44F332FF.5050809@appriss.com> User-Agent: mutt-ng/devel-r804 (FreeBSD) Subject: Re: Q) eclipse 3.2 (Callisto) 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, 29 Aug 2006 21:12:46 -0000 * David Sledge: > I feel the port itself is solid and ready for the PR to be sent. +1 > If there are I can submit it as eclipse-devel so that maybe a > larger user base will start working with it. [...] my only > question is to ask if it is ok to submit the PR without any > other ports that depend on the 3.1.2 version of eclipse being > updated first. Or do I need to submit the port of eclipse 3.2 > first so that the other ports can then be updated to use it? I suggest to request a repocopy of the current "java/eclipse" to "java/eclipse32", and submit your new port as an update of "java/eclipse32". Then if there is interest, the ports depending on "java/eclipse" can be progressively updated to "java/eclipse32" if relevant. Avoid the name "eclipse-devel" as it implies that the port is regularly updated for the latest Eclipse milestone. -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/