From owner-freebsd-current@FreeBSD.ORG Wed Sep 29 23:48:52 2004 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 55E1A16A4CE; Wed, 29 Sep 2004 23:48:52 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A088D43D3F; Wed, 29 Sep 2004 23:48:49 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i8TNlsUW021750; Wed, 29 Sep 2004 17:47:54 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 29 Sep 2004 17:49:14 -0600 (MDT) Message-Id: <20040929.174914.05878370.imp@bsdimp.com> To: deischen@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <20040929123100.GA600@electra.cse.Buffalo.EDU> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: kensmith@cse.Buffalo.EDU cc: tjr@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: HEADS-UP: Library version number bumps 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: Wed, 29 Sep 2004 23:48:52 -0000 In message: Daniel Eischen writes: : This has been mentioned before, but when breaking (or potentially : breaking) ABI, can we bump the version numbers to libfoo.YYYYMMDD? : Once release comes, we can move them back to SHLIB_MAJOR + 1 (or : even decide to keep them at SHLIB_MAJOR if ABI wasn't really broken). : This helps folks running HEAD so they can update their ports over time. In a lot of respects I like this idea. However, the unanswered question would be how to implement it. The bumps are easy to do (the version number is basically meaningless), but frequeny bumps have issues as well. Laying those aside for the moment, my concern is how do we do the 'one release comes' part there. How do we know if they are binary compatible or not? Wouldn't this tend to encourage people to make binary incompatible libraryes? Warner