On 31/03/14 19:18, Matthias Klose wrote: > I'm not in favour defaulting that again to > openjdk-7 or openjdk-6.
Having gcj on kfreebsd but openjdk for all other release architectures seems undesirable. I think over time, fewer packages will work at all with gcj (already eclipse-cdt, zookeeper, glpk-java). So I think we really need to try... > Steven, the kfreebsd port was backported from OpenJDK 8 by Damien. In > the past we had to wait for several months for updated kfreebsd patches > to get the openjdk-7 built again on these architectures, despite pinging > the kfreebsd porters. How did that change? I was inactive from Debian work around the time you pinged debian-bsd@, but I did eventually submit patches fixing the openjdk-7 build (#736291) - unfortunately applied too late for the change of default-jdk. > How can you make sure that > this won't repeat again? I can't promise I can keep up with new versions because I don't know how much breakage to expect. Only very simple changes were needed recently for u51, but it requires powerful build hardware running kfreebsd to work on and test this. It managed to migrate again to testing, and the update to IcedTea 2.4.6 prerelease didn't cause any new problems. I hope others can help with this work; Christoph and others have provided updated patches in the past. There is also an openjdk7 package in FreeBSD Ports, that we could borrow patches from if it breaks. (For example, the PortConfig issue that broke icedtea-web, was already fixed there). I'm signed up now to receive notifications of openjdk-7 package uploads and build failures, so I should at least know of problems a bit sooner, before you have to ping kfreebsd porters about it. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5339bc4a.4070...@pyro.eu.org
