Date: Wed, 04 Sep 2024 10:50:15 +0000 From: bugzilla-noreply@freebsd.org To: java@FreeBSD.org Subject: [Bug 279367] java/openjdk11 -- respect compiler and linker flags, allow building with gcc Message-ID: <bug-279367-8522-uhPpmYvN8Y@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-279367-8522@https.bugs.freebsd.org/bugzilla/> References: <bug-279367-8522@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279367 --- Comment #8 from Ronald Klop <ronald@FreeBSD.org> --- (In reply to Vladimir Druzenko from comment #7) See: https://wiki.freebsd.org/Java I don't know how active the group is nowadays. But things are not a "job of java@". It is a lot of voluntary work. The mechanism is to create a good patch and notify the maintainer of a port. After two weeks the patch can be committed by somebody else stating 'mainta= iner timeout' (this is documented somewhere). About 'doing this for java/openjdk*', I would advice to first commit this patch. Then create a new patch for the other JDKs. Possible using a new iss= ue. So this will not transform in a lingering project with a bigger and bigger scope. In the meantime we can learn from feedback on this change while roll= ing it out on the other JDK ports. This is how I roll out changes in my mongodb* ports. But, that is just my opinion. Cheers. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279367-8522-uhPpmYvN8Y>