From owner-freebsd-current@FreeBSD.ORG Sun Aug 26 16:49:00 2007 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 32A6416A468 for ; Sun, 26 Aug 2007 16:49:00 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id C6C0013C468 for ; Sun, 26 Aug 2007 16:48:59 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l7QGmfE5014364; Sun, 26 Aug 2007 12:48:41 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.netplex.net [204.213.176.10]); Sun, 26 Aug 2007 12:48:41 -0400 (EDT) Date: Sun, 26 Aug 2007 12:48:41 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Yar Tikhiy In-Reply-To: <20070826073535.GD21352@comp.chem.msu.su> Message-ID: References: <20070824.172212.74696955.imp@bsdimp.com> <20070825053302.GG99474@comp.chem.msu.su> <20070825.093925.43008968.imp@bsdimp.com> <1188071752.1853.44.camel@neo.cse.buffalo.edu> <20070826073535.GD21352@comp.chem.msu.su> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Ken Smith , current@freebsd.org, "M. Warner Losh" Subject: Symbol versioning conventions (was Re: cvs commit: src/lib/libc/gen ...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Aug 2007 16:49:00 -0000 On Sun, 26 Aug 2007, Yar Tikhiy wrote: > > But, anyway, there are at least three people in the project who > misundertood the intended role of symbol versioning. Besides yours > truly, a humble developer, there are a core team member and a release > engineer among them. This may be a sign that some decisions regarding > symbol versioning, which is a rather central feature for developers > and code contributors, haven't had enough exposure. Perhaps we've > just missed some important discussions on the lists, but symbol > versioning is a long-term feature and as such it deserves a document > describing in detail how to use it in our project. I've think I've stated in replies to commit mail that symbol versioning isn't meant as a crutch to aid -current developers, but that is neither written down or documented and was probably over a year ago. > The technical side of symbol versioning puts few limitations on how > one can use it, the rest being a matter of policy. Of course, the > choice of the policy is important and can have far-reaching > consequences, such as getting us into a complete mess or making us > technology champs like Linux and Sun. :-) Now all our symbols still > are at FBSD_1.0, and it isn't late yet to work out such a policy. > Again, it will make an excellent thread on -arch. Here it is on -current, feel free to redirect it to arch. I updated my notes on symbol versioning - see "Version naming conventions" on downwards at: http://people.freebsd.org/~deischen/symver/freebsd_versioning.txt Feel free to cut&paste anything from it in replies. -- DE