[SUGGEST] Reform eclipse and eclipse related ports

[Vizion]

On Monday 17 October 2005 05:53,  the author Ian G contributed to the dialogue 
on-
 Re: [SUGGEST] Reform eclipse and eclipse related ports: 

>(To all)
>
>Wes Peters wrote:
>> That's exactly the point I was (and am) trying to argue against.  I
>> have to resort to 'make search' to find emacs tools these days  because
>> they've been thrown all over the ports system by well-meaning  but
>> misguided contributors, and I'd hate to see that happen to  eclipse
>> tools too.
>
>As the directory structure imposes Big->Small naming
>on the ports, and this is always going to be inadequate.
>Many ports will have multiple namings and multiple
>ways of indexing that make lots of sense.  The directory
>structure gives one indexing and one name only though.
>
>The problem is not where Eclipse or a plugin is located,
>rather, it is that the directory structure cannot support
>anything more complex than the simplest naming schemes.

So what could be more simple than /usr/ports/eclipse?

>
>Moving Eclipse does not change this, only improving
>the search tools can help here.  So what is needed
>is something that deals with:
>
>    searchports eclipse plugin python
>
>or somesuch.
>
>iang
>
>_______________________________________________
>freebsd-java at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-java
>To unsubscribe, send any mail to "freebsd-java-unsubscribe at freebsd.org"

-- 
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.