From owner-cvs-all@FreeBSD.ORG Fri Oct 26 18:21:11 2007 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D24C16A417; Fri, 26 Oct 2007 18:21:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 7D61813C4C2; Fri, 26 Oct 2007 18:21:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 216251088-1834499 for multiple; Fri, 26 Oct 2007 14:23:36 -0400 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l9QIKdC3037881; Fri, 26 Oct 2007 14:20:52 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Ken Smith Date: Fri, 26 Oct 2007 12:24:40 -0400 User-Agent: KMail/1.9.6 References: <200710150951.l9F9pUm7026506@repoman.freebsd.org> <200710261141.51639.jhb@freebsd.org> <1193414454.7390.20.camel@opus.cse.buffalo.edu> In-Reply-To: <1193414454.7390.20.camel@opus.cse.buffalo.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710261224.41369.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 26 Oct 2007 14:20:53 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/4600/Fri Oct 26 10:02:30 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Scott Long , src-committers@freebsd.org, d@delphij.net, Andrey Chernov , obrien@freebsd.org, cvs-all@freebsd.org, cvs-src@freebsd.org Subject: Re: cvs commit: src/lib/libc/locale utf8.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2007 18:21:11 -0000 On Friday 26 October 2007 12:00:54 pm Ken Smith wrote: > On Fri, 2007-10-26 at 11:41 -0400, John Baldwin wrote: > > On Friday 26 October 2007 10:53:47 am David O'Brien wrote: > > > On Thu, Oct 25, 2007 at 05:31:03PM -0400, Ken Smith wrote: > > > > What we need to try and avoid unless *absolutely* *necessary* is the > > > > part Scott quoted above - binaries compiled on 6.3-REL should work on > > > > 6.2-REL unless there was a really big issue and the solution to that > > > > issue required us to break that. The reason is simple, people should be > > > > able to continue running 6.2-REL "for a while" and still be able to > > > > update their packages from packages-6-stable even after portmgr@ starts > > > > using a 6.3-REL base for the builds > > > > > > This is news to me. > > > I've never heard that we're that concerned with forward compatability > > > even on a RELENG branch. We do not break the ABI for backwards > > > compatability - in that everything (including kernel modules) that ran on > > > 6.2 must run on 6.3. > > > > Agreed. The solution to the shared /usr/local problem is to use the oldest > > version for /usr/local. That has always been the case. Forwards > > compatiblity (what you are asking for) is significantly harder to guarantee > > since accurately predicting the future isn't much a science. > > > > Yeah, sorry. I guess I've been a bit grumpy the past couple days and > over-stated the "*absolutely* *necessary*" part above. It should have > read "*necessary*", not "*absolutely* *necessary*". > > I'd just like us to question if it's necessary here. Is there a good > enough way to do this without causing the breakage? I sorta liked > Warren's question. Does this stuff need to be inlined and if not would > that solution avoid the breakage? I can agree that in this instance it would be nice to keep RELENG_7 and HEAD from diverging too much right now. I was more concerned about there being a new general policy. Are you really sure you want forwards compat and not just backwards compat ABI? -- John Baldwin