From owner-freebsd-java@FreeBSD.ORG Sun Oct 16 16:27:51 2005 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 424EE16A41F for ; Sun, 16 Oct 2005 16:27:51 +0000 (GMT) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CC2A43D55 for ; Sun, 16 Oct 2005 16:27:51 +0000 (GMT) (envelope-from marquis@roble.com) Date: Sun, 16 Oct 2005 09:27:50 -0700 (PDT) From: Roger Marquis To: freebsd-java@freebsd.org In-Reply-To: <20051016120045.C6E3A16A422@hub.freebsd.org> Message-ID: <20051016085915.R95131@roble.com> References: <20051016120045.C6E3A16A422@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [SUGGEST] Reform eclipse and eclipse related ports 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: Sun, 16 Oct 2005 16:27:51 -0000 Vizion > My solution is not popular even if it is logical. Honestly David, until you can make a better case your solution doesn't seem logical either. >I say the ports structure needs a strategy that takes account of >the reality of tools such as eclipse and soes not hesititate to >create entirely new categories to meet those new neeeds. Before doing that you really need to define what constitutes a port category i.e, a set of rules which can universally applied. This definition would need to encompass all ports, not just the one you're concerned about today, and do so in a way that is self-evident and at has some consensus among port maintainers. > We now need something like > ports/eclipse That would be the worst solution I could think of, but thanks for making your special interest clear. We can see by this it is a religious issue and the integrity of the ports collection is less important than your particular application. Since you are not similarly advocating ports/netbeans or ports/emacs the proposition is logically indefensible. > But this view does not dit well with those who feel there is a virtue in > preserving the existing structure which I cannot help but regard as an > anachronism for these newly emerging frameworks which do not fit well into > the traditional structure. You've outlined several possible frameworks where there's really only room for one. Choose wisely. [ ] existing [ ] emerging [ ] traditional [ ] structure -- Roger Marquis Roble Systems Consulting http://www.roble.com/