From owner-freebsd-java@FreeBSD.ORG Mon Oct 17 15:01:55 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 3C59816A41F for ; Mon, 17 Oct 2005 15:01:55 +0000 (GMT) (envelope-from xvalen@atlas.cz) Received: from tron.kn.vutbr.cz (tron.kn.vutbr.cz [147.229.191.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 738FA43D49 for ; Mon, 17 Oct 2005 15:01:53 +0000 (GMT) (envelope-from xvalen@atlas.cz) Received: from a03-0622d.kn.vutbr.cz (a03-0622d.kn.vutbr.cz [147.229.214.112]) by tron.kn.vutbr.cz (8.12.9p2/8.12.9) with SMTP id j9HF1pP3028225 for ; Mon, 17 Oct 2005 17:01:52 +0200 (CEST) (envelope-from xvalen@atlas.cz) Date: Mon, 17 Oct 2005 17:01:46 +0200 From: Petr Valenta To: freebsd-java@freebsd.org Message-Id: <20051017170146.60b1b90b.xvalen@atlas.cz> In-Reply-To: <200510161310.18807.vizion@vizion.occoxmail.com> References: <200510150015.j9F0ExKr085847@sakura.ninth-nine.com> <5739E97B-7EDC-4971-9EA5-01A44688A981@softweyr.com> <43522953.6050700@ebs.gr> <200510161310.18807.vizion@vizion.occoxmail.com> X-Mailer: Sylpheed version 2.1.3 (GTK+ 2.6.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.70, clamav-milter version 0.70j X-Spam-Flag: NO X-Scanned-By: milter-spamc/0.19.268 (tron [147.229.191.152]); Mon, 17 Oct 2005 17:01:52 +0200 X-Spam-Status: NO, hits=0.10 required=6.00 X-Spam-Level: X-Spam-Report: Spam detection software, running on the system "tron.kn.vutbr.cz", has tested this incoming email. See other headers to know if the email has beed identified as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or block similar future email. If you have any questions, see the administrator of that system for details. ____ Content analysis details: (0.1 points, 6.0 required) ____ pts rule name description ---- ---------------------- -------------------------------------------- 0.9 DATE_MISSING Missing Date: header -0.7 BAYES_10 BODY: Bayesian spam probability is 10 to 20% [score: 0.1629] ____ 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: Mon, 17 Oct 2005 15:01:55 -0000 On Sun, 16 Oct 2005 13:10:12 -0700 Vizion wrote: > On Sunday 16 October 2005 03:20, the author Panagiotis Astithas contributed > to the dialogue on- > Re: [SUGGEST] Reform eclipse and eclipse related ports: > > >Wes Peters wrote: > >> On Oct 15, 2005, at 2:39 AM, Panagiotis Astithas wrote: > >>> Mark Linimon wrote: > >>>> On Fri, Oct 14, 2005 at 09:15:07PM -0700, Wes Peters wrote: > >>>>> I don't mind moving the eclipse ports from java to devel, but all > >>>>> the other eclipse ports are add-ins to eclipse and should probably > >>>>> be classified along with eclipse. > >>>> > >>>> [adding freebsd-java to the Cc:] > >>>> For some background, there's been on-and-off discussion on -java > >>>> about how the java category was never really a good idea. None of > >>>> the other languages have their own primary category. In particular > >>>> we've completely failed to train our users to send 'java' PRs only > >>>> for problems with the JVMs and 'ports' PRs for things in ports/java. > >>>> > >>>>> In particular, if eclipse is a 'devel' tool, I don't see how CDT > >>>>> and phpeclipse are editors. GEF isn't a graphics library, it's a > >>>>> graphical emulation framework for eclipse, which is (again) a > >>>>> development tool. > >>> > >>> Although I agree with everything you say here, I can't see how this > >>> is an argument against the fact that GEF and CDT most probably belong > >>> to devel. Unless I'm mistaken and you were not making one? > >> > >> I was making an argument that regardless of where eclipse migrates too, > >> all of it's little pieces should go right along with it, rather than > >> getting spread all over the ports system. > > > >Since you snipped Mark's reply in your quote, let me clarify that my > >comments above were directed to Mark and I agree with your point. > >However I'm not sure whether there has to be a strict rule that every > >eclipse-foo port should go in the same category. Perhaps the emacs > >precedent should be followed. See below. > > > >Norikatsu Shigemura wrote: > > > On Sat, 15 Oct 2005 09:14:59 +0900 (JST) > > > > > > Norikatsu Shigemura wrote: > > >>Hi eclipse and eclipse related ports maintainers and users! > > >> Some time ago, someone suggested that eclipse and eclipse > > >> related ports should be located on proper categories. I > > >> think so. So I suggest following repocopy list. Anyone, > > >> do you have any idea? > > > > > > Oops, I missed. Eclipse is very similar to Emacs: > > > 1. IDE > > > Emacs is a one of IDE(or platform). And anyone doesn't > > > think that it is ONLY a elisp interpreter. But it is > > > a editor. So I think that it is no problem that Eclipse > > > may be categolize to editors. > > > > > > 2. Extension-able > > > Emacs has many extention modules like news reader, language > > > support, games, ... > > > > > > 3. Mode > > > Emacs has many mode for descriptions like C, Perl, Java, ... > > > > > > 4. others > > > It must be that there are other similar feature:-). > > > > > > java/eclipse -> editors/eclipse > > > java/eclipse-EPIC -> editors/eclipse-EPIC > > > java/eclipse-cdt -> editors/eclipse-cdt > > > java/eclipse-checkstyle -> devel/eclipse-checkstyle > > > java/eclipse-clay-core -> databases/eclipse-clay-core > > > java/eclipse-devel -> editors/eclipse-devel > > > java/eclipse-emf -> editors/eclipse-emf > > > java/eclipse-examples -> devel/eclipse-examples > > > java/eclipse-gef -> editors/eclipse-gef > > > java/eclipse-gef-examples -> editors/eclipse-gef-examples > > > java/eclipse-langpack -> editors/eclipse-langpack > > > java/eclipse-log4e -> editors/eclipse-log4e > > > java/eclipse-lomboz -> devel/eclipse-lomboz > > > java/eclipse-pmd -> devel/eclipse-pmd > > > java/eclipse-quantum -> databases/eclipse-quantum > > > java/eclipse-sqlexplorer -> databases/eclipse-sqlexplorer > > > java/eclipse-sysdeo-tomcat -> www/eclipse-sysdeo-tomcat > > > java/eclipse-uml -> editors/eclipse-uml > > > java/eclipse-v4all -> editors/eclipse-v4all > > > java/eclipse-vep -> editors/eclipse-vep > > > java/eclipse-vep-examples -> editors/eclipse-vep-examples > > > java/eclipse-viplugin -> editors/eclipse-viplugin > > > java/eclipseme -> devel/eclipseme > > > java/phpeclipse -> editors/phpeclipse > > > >This sounds fine, too. > Sounds crazy to me... > Scattering eclipse tools over the whole ports collections is, to my mind, a > retrograde, rather than a positive step. There are another 290 pus eclipse > tools to bring on board!! > I would continue to advocate for a single collection > david I agree, many people don't need eclipse and puting it into whole port collection is bad because there will be no way to disable fetching eclipse-* with cvsup...I think that /usr/ports/eclipse/ will be the best solution. Petr > > -- > 40 yrs navigating and computing in blue waters. > English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. > Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after > completing engineroom refit. > _______________________________________________ > freebsd-java@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-java > To unsubscribe, send any mail to "freebsd-java-unsubscribe@freebsd.org" > > >