From owner-freebsd-current@FreeBSD.ORG Mon Feb 4 19:37:14 2008 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E48C616A417; Mon, 4 Feb 2008 19:37:14 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF6713C442; Mon, 4 Feb 2008 19:37:14 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.14.2/8.14.1) with ESMTP id m14J80WS041773; Mon, 4 Feb 2008 14:08:00 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.14.2/8.14.1/Submit) id m14J80oW041772; Mon, 4 Feb 2008 14:08:00 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Mon, 4 Feb 2008 14:08:00 -0500 From: David Schultz To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Message-ID: <20080204190800.GA41339@VARK.MIT.EDU> Mail-Followup-To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , Daniel Eischen , Kostik Belousov , threads@FreeBSD.ORG, Peter Wemm , current@FreeBSD.ORG References: <861w7um5o5.fsf@ds4.des.no> <20080203162918.GK57756@deviant.kiev.zoral.com.ua> <20080203121112.426a8c25@kan.dnsalias.net> <86zlugeqaz.fsf@ds4.des.no> <86r6fsd55s.fsf@ds4.des.no> <86abmgd4gl.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86abmgd4gl.fsf@ds4.des.no> Cc: Daniel Eischen , Kostik Belousov , current@FreeBSD.ORG, Peter Wemm , threads@FreeBSD.ORG Subject: Re: Symbol versioning errors in libthr X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 04 Feb 2008 19:37:15 -0000 On Mon, Feb 04, 2008, Dag-Erling Smørgrav wrote: > Daniel Eischen writes: > > Dag-Erling Smørgrav writes: > > > (unless you can show that it's actually harmful in some way?) > > Please do not bump private, it was never meant to be bumped like this. > > This is not substantiation, this is the old monkey telling the young > monkey "this is the way it's always been done". > > With all due respect to the old monkey, the young monkey simply can't > understand why FBSD and FBSDprivate should be assymetric. The private namespace is a repository for symbols that we don't intend to support across releases; these symbols may change or go away, and applications shouldn't use them directly. Making multiple private namespaces implies that the private namespaces *are* stable according to some definition, hence why we need more than one of them. Having stronger requirements for private namespaces would seem to defeat the purpose and create more work for people, principally Dan, who is still working with re@ to get the FBSD_1.0 symbols right for 7.0-RELEASE. Perhaps you could explain what stability requirements you have in mind for FBSDPrivate_X.Y here. > The young monkey would also like the old monkey to explain to him what > harm will come of this (the young monkey has asked this already, but the > old monkey has declined to respond). > > Finally, the young monkey would like to point out that this is all very > poorly documented. While aware of the freebsd_versioning.txt document > written by the old monkey, the young monkey can't find anything in it > about private symbol spaces. > > If the old monkey is in any way offended by this, he is free to > s/old/mature and experienced/ :) This is a little bit more sarcastic and pretentious than needed. Have a banana. `-=-' --the small monkey in the corner