Date: Sat, 11 Jun 2011 09:29:16 -0600 (MDT) From: Gerald Pfeifer <gerald@pfeifer.com> To: Greg Larkin <glarkin@FreeBSD.org> Cc: cvs-ports@FreeBSD.org, Gerald Pfeifer <gerald@FreeBSD.org>, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/lang/gcc46 Makefile distinfo pkg-plist Message-ID: <alpine.LNX.2.00.1106110908400.3409@gerinyyl.fvgr> In-Reply-To: <4DE83021.8030803@FreeBSD.org> References: <201106022211.p52MBmoH094389@repoman.freebsd.org> <4DE83021.8030803@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2 Jun 2011, Greg Larkin wrote: > I guess I can close PR 157396 now? Shall I assume that you'd still > like to remove Java support from the lang/gcc* ports, if possible? I think you can close the PR, yes. As for removing Java support, I think having one instance of lang/gcc* with Java support should be sufficient, so now with lang/gcc46 featuring that, can we remove that from lang/gcc45? (That only means changing the USE_GCC line in pkdftk, I think? > Building pdftk with OpenJDK is the preferred solution. If that doesn't > work, I want to test if I can kick off a gcc+gcj build from the pdftk > port, use it to build a static pdftk, then clean everything up without > permanently installing gcc+gcj. Let me know if you think that will be > too messy. That sounds really heavy for users of pdftk, and I think we should have a version of lang/gcc that does not require that. BUT, that also could be a special version, a slave port with some special option set that the vast majority of users odes not need to worry about. Something for later, I guess; for now removing Java support from lang/gcc45 (and first adjusting pdftk) would be the next step I think? Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LNX.2.00.1106110908400.3409>