| Re: [eclipse-dev] official platform requirements |
Kim Moir said the following: > Here's a document on the process (It's a bit out of date). In addition to > contributing the SWT fragment, you need to compile the launcher fragment and > contribute it. > > http://wiki.eclipse.org/Platform-releng-faq#I_would_like_to_recompile_eclipse_on_a_platform_that_is_not_currently_supported._What_is_the_best_approach_to_this.3F__How_can_I_ensure_that_the_community_can_use_my_work.3F Thank you for this information. > What ws-os-arch platform are you interested in contributing? Googling you, I > assume FreeBSD? Yes. My email address is kind of a giveaway too :-) > To be honest, we haven't had success in the past with community contributions > of new platforms. It seems like people make the initial contribution and then > decide not to update it which causes problems for the build because the > fragments become out of sync and compile errors result. So I must emphasize > that contributing a new platform is a ongoing compiling, testing and bug > triaging commitment :-) Let me know how if you have any questions on getting > started. FreeBSD community members have been rather successfully maintaining a port of Eclipse to FreeBSD for a while now. Here you can see current state of the port and its history: http://www.freebsd.org/cgi/cvsweb.cgi/ports/java/eclipse/ http://www.freebsd.org/cgi/cvsweb.cgi/ports/java/eclipse-devel/ However, I do agree that doing ports of release and doing continuous platform maintenance and support are two sufficiently different things. I need to get back to FreeBSD Eclipse community with this. Thank you. P.S. Is there such a thing as a "deltapack-only platform"? -- Andriy Gapon