From owner-svn-src-head@FreeBSD.ORG Wed Nov 6 19:18:28 2013 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 420F9845; Wed, 6 Nov 2013 19:18:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1763C264A; Wed, 6 Nov 2013 19:18:28 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 294F0B981; Wed, 6 Nov 2013 14:18:27 -0500 (EST) From: John Baldwin To: Adrian Chadd Subject: Re: svn commit: r257696 - in head: libexec/rbootd share/man/man9 sys/compat/svr4 sys/net sys/sys Date: Wed, 6 Nov 2013 12:08:35 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <201311051029.rA5ATmmM017799@svn.freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201311061208.36029.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 06 Nov 2013 14:18:27 -0500 (EST) Cc: "svn-src-head@freebsd.org" , svn-src-all , Gleb Smirnoff , "src-committers@freebsd.org" , Peter Wemm X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Nov 2013 19:18:28 -0000 On Wednesday, November 06, 2013 12:00:59 pm Adrian Chadd wrote: > I think the important thing here is that there _are_ organisations > that rely on some reasonable attempt at supporting historical APIs > where needed. > > This IMHO should've explicitly gone into a compat macro for people who > want support of this older stuff. > > My suggestion for a saner way to handle this deprecation schedule: > > * do the announce - I'd have to go looking for that, but we should be > placing these somewhere obvious (like a wiki page that lists > deprecated APIs in order, with the date/release they're going to be > deprecated); > * deprecate the userland use of the ioctl values first so they use the > newer API; > * deprecate the kernel API after the announced amount of time, hiding > things behind COMPAT_xxx as appropriate. Actually, Gleb has mostly done this, it's just that the last step turned into an rm rather than moving under an #ifdef COMPAT_xxxx. -- John Baldwin