Date: Tue, 17 Dec 2013 21:55:33 +0100 From: Tijl Coosemans <tijl@FreeBSD.org> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r336343 - in head: . Mk/Uses Message-ID: <20131217215533.3c0d9fcb@kalimero.tijl.coosemans.org> In-Reply-To: <alpine.LSU.2.11.1312160847420.2366@tuna.site> References: <201312131322.rBDDMWZC038800@svn.freebsd.org> <alpine.LSU.2.11.1312160847420.2366@tuna.site>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Dec 2013 09:54:33 +0100 (CET) Gerald Pfeifer wrote: > On Fri, 13 Dec 2013, Tijl Coosemans wrote: >> Log: >> New USES=fortran to replace USE_FORTRAN. > > I was already surprised when Bapt introduced USES=compiler and later > made changes to the default version of GCC there without ever giving > me a heads up. Now USE_FORTRAN, which I maintain, is being replaced > without you reaching out to me. > > And there is an aweful lot of redundancy and even some inconsistency now. > > Not that I oppose in principle, or would have, but a little bit more > communications and collaboration would be nice. > > Gerald (sad) > > > PS: I'm starting vacation as we speak and will have limited connectivity > the coming weeks, and likely none from the 17th to the 27th. It was discussed on current@ (libc++ vs. libstdc++ usage in the ports tree) and I CCed you when I had analysed the problem but apparently not when I submitted a patch. Sorry about that. The reason I chose to create USES=fortran is because several other languages already use the USES framework and because the solution to the Octave problem was to separate the selection of the Fortran compiler from the selection of the C/C++ compiler. To address the redundancy I think there are a number of things we can do: - I expect converting Fortran ports will be relatively straightforward so the Fortran bits in bsd.gcc.mk can eventually be removed. - Maybe the C/C++ bits in bsd.gcc.mk can be moved to compiler.mk? I like the way compiler.mk is built around features instead of versions. - Use the bsd.default-versions.mk framework to set GCC_DEFAULT. This allows users to set their preferred version of GCC in make.conf and provides a central place where both fortran.mk and compiler.mk can pick up the default GCC version instead of each having it hardcoded.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131217215533.3c0d9fcb>