Date: Wed, 4 Oct 2006 09:24:50 +0200 From: "Massimo Lusetti" <mlusetti@gmail.com> To: "David Sledge" <dsledge@appriss.com> Cc: Palle Girgensohn <girgen@freebsd.org>, freebsd-java@freebsd.org Subject: Re: Eclipse 3.2 port (java/eclipse32) Message-ID: <a6647e120610040024u642781d0s13eab2454248b29e@mail.gmail.com> In-Reply-To: <452286C2.3030902@appriss.com> References: <768690DD58883C4FAA0C089A534F94DF2054DE@intexch02.int.appriss.com> <54A56D47DC749F45C4291FD0@rambutan.pingpong.net> <452286C2.3030902@appriss.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/3/06, David Sledge <dsledge@appriss.com> wrote: > Working on the build for 3.2.1 now. Hoping to have it done by the end of > the day. We talked about updating the the old port on this mailing list > and more people seemed to want it to be a separate port so we did not > break the dependencies. I am getting more and more emails now supporting > to update the existing eclipse port. I have no problem with that. I will > ask again how many people would prefer updating the original eclipse > port versus creating a new port? Please comment on this ASAP as I am > working on an update to eclipse 3.2.1. FWIW I guess the right way wuold be to upgrade the original port as anyway if you upgrade eclipse SDK you have to (in a way or the other) upgrade all other plugins etc... So a big warning or a broken flag on dependandt (broken) ports should suffice, IMHO, you can read this as "should suffice to me" :) Regards and thanks for the great work. -- Massimo http://meridio.blogspot.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a6647e120610040024u642781d0s13eab2454248b29e>