From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 128172 invoked by alias); 29 Oct 2016 18:19:05 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 128162 invoked by uid 89); 29 Oct 2016 18:19:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=thorough, weekly, approximately, Hx-languages-length:1590 X-HELO: relay1.mentorg.com Date: Sat, 29 Oct 2016 18:19:00 -0000 From: Joseph Myers To: Thorsten Kukuk CC: Subject: Re: [PATCH] deprecate libnsl (Version 3) In-Reply-To: <20161029103834.GA1348@suse.de> Message-ID: References: <20160406094807.GA23625@suse.de> <20160408131142.GA7627@suse.de> <20160623064622.GA27378@suse.de> <20161029103834.GA1348@suse.de> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2016-10/txt/msg00589.txt.bz2 On Sat, 29 Oct 2016, Thorsten Kukuk wrote: > Hi, > > since I still got no feedback about the deprecation patches > for sunrpc and libnsl and no try was made to get it into > the last glibc version, I assume nobody is interested in > really deprecating this old IPv4 only code to make it easier > for other projects and users to switch to IPv6? Could you give the URL for the latest patch versions, and for any relevant discussions that might indicate consensus, lack thereof or other relevant issues, when pinging a patch (and pings should be approximately weekly, including the URL every time, with patches updated if they no longer apply cleanly to current sources)? Please make sure the latest version is self-contained with a full write-up explaining it so that there's no need to refer back to previous versions / other emails for an understanding of the change being made and the rationale for the change and the design used (and that it includes NEWS entries pointing to any relevant replacement libraries for users, etc.). I suspect there's a lack of people familiar with the code and ready to judge desirability of the change, which makes it especially important to have a thorough self-contained explanation of everything included with the patch (the NEWS entries of course should have such information aimed at people building/using glibc so it's immediately obvious where they should go to get libnsl, libnss* etc. and what changes to their code they might need to use such replacements). -- Joseph S. Myers joseph@codesourcery.com