From owner-freebsd-arch@FreeBSD.ORG Tue May 6 10:55:57 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 333E537B401 for ; Tue, 6 May 2003 10:55:57 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6059F43F85 for ; Tue, 6 May 2003 10:55:56 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id AE30566; Tue, 6 May 2003 12:55:55 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id 468A278C66; Tue, 6 May 2003 12:55:57 -0500 (CDT) Date: Tue, 6 May 2003 12:55:57 -0500 From: "Jacques A. Vidrine" To: David O'Brien Message-ID: <20030506175557.GE79167@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , David O'Brien , freebsd-arch@FreeBSD.org References: <20030501182820.GA53641@madman.celabo.org> <20030503201409.GA41554@dragon.nuxi.com> <20030505175428.GA19275@madman.celabo.org> <20030506170919.GD36798@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030506170919.GD36798@dragon.nuxi.com> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 cc: freebsd-arch@FreeBSD.org Subject: Re: Re: `Hiding' libc symbols X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 17:55:57 -0000 On Tue, May 06, 2003 at 10:09:19AM -0700, David O'Brien wrote: > On Mon, May 05, 2003 at 12:54:28PM -0500, Jacques A. Vidrine wrote: > > > > I'm backing out the commit in good faith and in the hopes that the > > > > big picture comes more clearly into focus. > > > > > > Thanks. > > > > Do you also want to `fix' the other ports that define their own strlcpy? > > Ports have maintainers. Please create a PR for them. But gee, the problem is that the ports themselves are not really in error, unless one is a standards fascist that believes that an application can never define any function that might be in some standard's namespace. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se