Date: Sun, 29 Jul 2012 17:11:14 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: Brendan Fabeny <bf1783@gmail.com>, freebsd-ports@FreeBSD.org, Kevin Oberman <kob6558@gmail.com> Subject: Re: lang/gcc46 Message-ID: <5015D122.4040608@FreeBSD.org> In-Reply-To: <alpine.LNX.2.00.1207300152200.2533@gerinyyl.fvgr> References: <CAGFTUwNbj0mDrdu40dwkmECLhrc0Uwap=8UKi=tbBgRCTvZTMQ@mail.gmail.com> <alpine.LNX.2.00.1207300152200.2533@gerinyyl.fvgr>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/29/2012 16:55, Gerald Pfeifer wrote:
> lang/gcc and lang/gcc46 should be fully compatible, without rebuilds
> necessary. Only when lang/gcc is going to move to GCC 4.7 later this
> year would I consider that.
IMO this highlights the issue that unversioned instances of ports that
really need versioning (like gcc) are a bad idea. It's much better for
users to be able to tie their installations to a particular version, and
then only update when they need to. The fact that someday in the future
users who innocently upgrade lang/gcc will suddenly find that everything
relying on libgcc at runtime is now broken pretty much speaks for itself.
Perl is the shining example of how the versioning strategy works well,
lang/python and lang/php5 are examples of where it's not meeting our
users' needs.
Doug
--
I am only one, but I am one. I cannot do everything, but I can do
something. And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5015D122.4040608>