Date: Sun, 16 Oct 2005 13:39:15 -0700 From: Vizion <vizion@vizion.occoxmail.com> To: freebsd-ports@freebsd.org Subject: Re: [SUGGEST] Reform eclipse and eclipse related ports Message-ID: <200510161339.16247.vizion@vizion.occoxmail.com>
next in thread | raw e-mail | index | archive | help
On Sunday 16 October 2005 03:20, =A0the author Panagiotis Astithas contribu= ted=20 to the dialogue on- =A0Re: [SUGGEST] Reform eclipse and eclipse related ports:=20 >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 =A0other eclipse ports are add-ins to eclipse and should =A0proba= bly >>>>> be =A0classified 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. =A0None of >>>> the other languages have their own primary category. =A0In 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. =A0GEF isn't a graphics library, it's =A0a >>>>> 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 =A0belong >>> to devel. Unless I'm mistaken and you were not making one? >> >> I was making an argument that regardless of where eclipse migrates =A0to= o, >> all of it's little pieces should go right along with it, rather =A0than >> 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 <nork@freebsd.org> wrote: > >>Hi eclipse and eclipse related ports maintainers and users! > >>=A0=A0=A0=A0Some time ago, someone suggested that eclipse and eclipse > >>=A0=A0=A0=A0related ports should be located on proper categories. =A0I > >>=A0=A0=A0=A0think so. =A0So I suggest following repocopy list. =A0Anyon= e, > >>=A0=A0=A0=A0do you have any idea? > > > > =A0=A0=A0=A0Oops, I missed. =A0Eclipse is very similar to Emacs: > > =A0=A0=A0=A01. IDE > > =A0=A0=A0=A0 =A0 Emacs is a one of IDE(or platform). =A0And anyone does= n't > > =A0=A0=A0=A0 =A0 think that it is ONLY a elisp interpreter. =A0But it is > > =A0=A0=A0=A0 =A0 a editor. =A0So I think that it is no problem that Ecl= ipse > > =A0=A0=A0=A0 =A0 may be categolize to editors. > > > > =A0=A0=A0=A02. Extension-able > > =A0=A0=A0=A0 =A0 Emacs has many extention modules like news reader, lan= guage > > =A0=A0=A0=A0 =A0 support, games, ... > > > > =A0=A0=A0=A03. Mode > > =A0=A0=A0=A0 =A0 Emacs has many mode for descriptions like C, Perl, Jav= a, ... > > > > =A0=A0=A0=A04. others > > =A0=A0=A0=A0 =A0 It must be that there are other similar feature:-). > > > > =A0=A0=A0=A0java/eclipse =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0-> editors/ecli= pse > > =A0=A0=A0=A0java/eclipse-EPIC =A0 =A0 =A0 =A0 =A0 -> editors/eclipse-EP= IC > > =A0=A0=A0=A0java/eclipse-cdt =A0 =A0 =A0 =A0 =A0 =A0-> editors/eclipse-= cdt > > =A0=A0=A0=A0java/eclipse-checkstyle =A0 =A0 -> devel/eclipse-checkstyle > > =A0=A0=A0=A0java/eclipse-clay-core =A0 =A0 =A0-> databases/eclipse-clay= =2Dcore > > =A0=A0=A0=A0java/eclipse-devel =A0 =A0 =A0 =A0 =A0-> editors/eclipse-de= vel > > =A0=A0=A0=A0java/eclipse-emf =A0 =A0 =A0 =A0 =A0 =A0-> editors/eclipse-= emf > > =A0=A0=A0=A0java/eclipse-examples =A0 =A0 =A0 -> devel/eclipse-examples > > =A0=A0=A0=A0java/eclipse-gef =A0 =A0 =A0 =A0 =A0 =A0-> editors/eclipse-= gef > > =A0=A0=A0=A0java/eclipse-gef-examples =A0 -> editors/eclipse-gef-exampl= es > > =A0=A0=A0=A0java/eclipse-langpack =A0 =A0 =A0 -> editors/eclipse-langpa= ck > > =A0=A0=A0=A0java/eclipse-log4e =A0 =A0 =A0 =A0 =A0-> editors/eclipse-lo= g4e > > =A0=A0=A0=A0java/eclipse-lomboz =A0 =A0 =A0 =A0 -> devel/eclipse-lomboz > > =A0=A0=A0=A0java/eclipse-pmd =A0 =A0 =A0 =A0 =A0 =A0-> devel/eclipse-pmd > > =A0=A0=A0=A0java/eclipse-quantum =A0 =A0 =A0 =A0-> databases/eclipse-qu= antum > > =A0=A0=A0=A0java/eclipse-sqlexplorer =A0 =A0-> databases/eclipse-sqlexp= lorer > > =A0=A0=A0=A0java/eclipse-sysdeo-tomcat =A0-> www/eclipse-sysdeo-tomcat > > =A0=A0=A0=A0java/eclipse-uml =A0 =A0 =A0 =A0 =A0 =A0-> editors/eclipse-= uml > > =A0=A0=A0=A0java/eclipse-v4all =A0 =A0 =A0 =A0 =A0-> editors/eclipse-v4= all > > =A0=A0=A0=A0java/eclipse-vep =A0 =A0 =A0 =A0 =A0 =A0-> editors/eclipse-= vep > > =A0=A0=A0=A0java/eclipse-vep-examples =A0 -> editors/eclipse-vep-exampl= es > > =A0=A0=A0=A0java/eclipse-viplugin =A0 =A0 =A0 -> editors/eclipse-viplug= in > > =A0=A0=A0=A0java/eclipseme =A0 =A0 =A0 =A0 =A0 =A0 =A0-> devel/eclipseme > > =A0=A0=A0=A0java/phpeclipse =A0 =A0 =A0 =A0 =A0 =A0 -> editors/phpeclip= se > >This sounds fine, too. Sounds crazy to me... Scattering eclipse tools over the whole ports collections is, to my mind, a= =20 retrograde, rather than a positive step. There are another 290 pus eclipse= =20 tools to bring on board!! I would continue to advocate for a single collection david=20 =2D-=20 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Tauru= s. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal afte= r=20 completing engineroom refit.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510161339.16247.vizion>