From owner-freebsd-current@FreeBSD.ORG Tue Apr 26 11:20:57 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 140CB16A4CE for ; Tue, 26 Apr 2005 11:20:57 +0000 (GMT) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CC7143D55 for ; Tue, 26 Apr 2005 11:20:56 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j3QBKtmu008919; Tue, 26 Apr 2005 06:20:55 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <426E23E3.3020404@centtech.com> Date: Tue, 26 Apr 2005 06:20:03 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050325 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gary Jennejohn References: <200504261109.j3QB90Hr003349@peedub.jennejohn.org> In-Reply-To: <200504261109.j3QB90Hr003349@peedub.jennejohn.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: library problems with -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2005 11:20:57 -0000 Gary Jennejohn wrote: > Holm Tiffe writes: > >>Gary Jennejohn wrote: >> >>>It's not in UPDATING, but a change was recently made (can't say exactly >>>when) which affects %gs/%fs. If you're using -current then you really >>>should watch the commits, too! >>> >> >>Yes we should watch the commitlogs, but it's really bad behavior to brake >>that many of the installed Applications and not to mention this fact in >>UPDATING. That's what IMHO version numbers for. >> > > > If you'd been watching the commits then you would have seen that the > problem has already been resolved in -CURRENT and RELENG_5. I hate to be negative, but the general rule I've always seen (and I believe it is even in the handbook) is that you should subscribe to -CURRENT, and read UPDATING, since that is where notes like this would be. I've never once heard anyone say that I should be watching the commits too. See, the thing is, that I'm running -CURRENT not because I can whip out C code in a snap or help write the newest Flux Capacitating Fligamabob, but because I can help test and find bugs, debug, etc. So I may subscribe to the commits, but I will have little to no idea what I see in my inbox unless someone explicitly puts a comment in there saying "this is gonna break some stuff - look out for XYZ", which obviously isn't going to happen (and I wouldn't expect it to). I saw a little chatter about this on -arch, but I didn't see anything in UPDATING or on this list mentioning the problem was fixed until just now. I never complained, but it might be good practice to keep our 'watch list' for -CURRENT users to a minimum to help keep the number of -CURRENTers up. Take everything I just said with a grain of salt, I'm just a 'user'. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------