From owner-freebsd-arch@FreeBSD.ORG Wed Apr 13 16:43:28 2005 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 F192016A4CE; Wed, 13 Apr 2005 16:43:27 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3218943D5C; Wed, 13 Apr 2005 16:43:25 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [166.220.248.152] (DEN-166-220-248-152.goport.net [166.220.248.152] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3DGkVSM046068; Wed, 13 Apr 2005 10:46:32 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <425D4B48.4070801@samsco.org> Date: Wed, 13 Apr 2005 10:39:36 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Giorgos Keramidas References: <19268.1113403507@critter.freebsd.dk> <425D302C.1060006@samsco.org> <20050413152707.GA41331@orion.daedalusnetworks.priv> In-Reply-To: <20050413152707.GA41331@orion.daedalusnetworks.priv> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: arch@freebsd.org cc: Poul-Henning Kamp cc: re@freebsd.org cc: David Xu Subject: Re: HEADS-UP: Planning on deprecating libc_r for 6.0 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: Wed, 13 Apr 2005 16:43:28 -0000 Giorgos Keramidas wrote: > On 2005-04-13 08:43, Scott Long wrote: > >>Poul-Henning Kamp wrote: >> >>>>How about modifying the dynamic linker to print a warning to stderr, >>>>much like mktemp(3), but let the user disable it by setting an >>>>environment variable, like LD_WARN_LIBC_R_DISABLE or similar? >>> >>>The user can disable it by adding a line in libmap.conf so let us not >>>invent more handles to tweak but point the user at the right one. >> >>Well, the worry is that there are legacy apps out there that rely on >>features/bugs only found in libc_r, therefore the user can't just >>switch. > > > Exactly the reason why I like the idea of deprecation messages but also like > being able to disable them. It's not really impossible or unthought of that > it may take a stupidly long amount of time for a vendor to fix their broken > application that depends on a bug of a deprecated library *and* misbehaves > because of a message sent to stderr by the linker. > > Having said that, since this is being deprecated in 6.X, which is pretty much > "current" and people aren't really expected to jump on the FreeBSD-current > wagon if they use FreeBSD for production, how many people use libc_r now that > may be bitten by the deprecation messages? > Well, 6-CURRENT will turn to 6-STABLE in just a few months. It's not years in the future =-) Scott