From owner-freebsd-ports@FreeBSD.ORG Sat Jul 28 23:54:41 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 5AE61106564A for ; Sat, 28 Jul 2012 23:54:41 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id EBBD614F2A2; Sat, 28 Jul 2012 23:54:40 +0000 (UTC) Date: Sat, 28 Jul 2012 16:54:40 -0700 (PDT) From: Doug Barton To: Jerry In-Reply-To: <20120725183432.4e73b434@scorpio> Message-ID: References: <000601cd6a76$af1de6b0$0d59b410$@quicknet.nl> <50103781.8060904@FreeBSD.org> <20120725183432.4e73b434@scorpio> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-message-flag: Outlook -- Not just for spreading viruses anymore! OpenPGP: id=1A1ABC84 Organization: http://SupersetSolutions.com/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-ports@freebsd.org Subject: Re: FreeBSD Port: bash-4.2.28 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2012 23:54:41 -0000 On Wed, 25 Jul 2012, Jerry wrote: > On Wed, 25 Jul 2012 11:14:25 -0700 > Doug Barton articulated: > >> On 07/25/2012 08:03, Michael wrote: >>> Hello obrien, >>> >>> Any plans to update bash-4.2.28 up to patch level 037? >> >> Is there a specific bug fixed that you're interested in? > > The short answer would be what the hell difference does that make? We don't use that kind of language on the FreeBSD lists. > The > OP just wanted to know if the port was going to be updated to include > the newly released patches. The long answer is that he is interested in > getting the official patches to correct known problems with Bash. Who's > business is it what problem, real or potential that the OP is looking > to correct or prevent? Completely aside from my being thoroughly impressed with your mind-reading abilities, upgrading to the latest/greatest is not always the best strategy. Speaking generally, even things that are (nominally) strictly bug fixes can bring in new problems, and Bash patches are not always strictly bug fixes. There is also the issue that in FreeBSD we are generally more conservative about upgrading something from a known-stable version. As for my motivations for asking the question, there are at least 2. First, I don't see anything in the latest set of patches that I find particularly exciting, but I'm interested in the OP's perspective. Second, if the OP is actually being affected by one of the things that is patched, I know the maintainer would be interested in that. > Actually, the OP would be better served contacting the port maintainer > . Unlike Postfix that updates > in virtually real time, there is usually quite a lag between the time > Bash issues a patch and the time it makes it into the ports system. See above. hth, Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/