ken wrote:
Hi!
I ported eclipse 3.3.1 to FreeBSD and Greg registered it as eclipse-devel in
ports tree.
I updated eclipse-devel to 3.3.1.1 which is the latest stable version and am
about ready to ask Greg to update the eclipse-devel.
I recognized the bug [EMAIL PROTECTED] pointed out in 3.3.1.1, too and
included it to my eclipse-devel tree.
You'll find updated one at http://www.tydfam.jp/eclipse-devel3311.tgz for
your review.
_______________________________________________
freebsd-eclipse@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-eclipse
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Hey Ken,
Nice progress... glad to see you're still at it!
Greg: I know you mentioned holding 3.3 in -devel until the plugin ports
could be updated... is there anything happening, or likely to for that
matter? Ganymede will be upon us in no time and I for one would like to
see the ports get a little closer to "catch ye monkey" rather than
losing round.
I don't know how people would feel about setting a target date and those
which aren't ready for 3.3 could be reassigned as requiring 3.2; not a
ideal solution by any means; but nor is having the ports tree stuck on
3.2 perpetually.
I use a very limited set of plugins and those which I do use are all
installed via update sites, so my actual experience with the plugin
ports is about nil... perhaps someone closer to those projects might
have a more enlightened view.
Cheers all,
Mike.
_______________________________________________
freebsd-eclipse@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-eclipse
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
