From owner-freebsd-threads@FreeBSD.ORG Mon Feb 4 17:04:40 2008 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6280E16A420; Mon, 4 Feb 2008 17:04:40 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 1A02313C459; Mon, 4 Feb 2008 17:04:40 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id DAA21207E; Mon, 4 Feb 2008 18:04:31 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id CB0432049; Mon, 4 Feb 2008 18:04:31 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id B0BA6844A0; Mon, 4 Feb 2008 18:04:31 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Daniel Eischen References: <861w7um5o5.fsf@ds4.des.no> <20080203162918.GK57756@deviant.kiev.zoral.com.ua> <20080203121112.426a8c25@kan.dnsalias.net> <86zlugeqaz.fsf@ds4.des.no> Date: Mon, 04 Feb 2008 18:04:31 +0100 In-Reply-To: (Daniel Eischen's message of "Mon\, 4 Feb 2008 11\:55\:52 -0500 \(EST\)") Message-ID: <86r6fsd55s.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: threads@freebsd.org, Peter Wemm , current@freebsd.org Subject: Re: Symbol versioning errors in libthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2008 17:04:40 -0000 Daniel Eischen writes: > I question the bumping of FBSDprivate to 1.1. FBSDprivate is special, > it is only for use in our base system, and our supported method of > updating our system is buildworkd/buildkernel - so any changes to > FBSDprivate should be unnoticed. A whole lot of assumptions there. Bumping FBSDprivate costs nothing and might save our a***s down the road if one of those assumptions turn out to be false. (unless you can show that it's actually harmful in some way?) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no