Date: Sat, 5 Nov 2016 07:30:10 -0700 From: Alfred Perlstein <alfred@freebsd.org> To: Konstantin Belousov <kostikbel@gmail.com>, "Pedro F. Giffuni" <pfg@FreeBSD.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r308314 - head/usr.bin/sed Message-ID: <6d9123fb-2b0a-c4a4-c584-d71874074d47@freebsd.org> In-Reply-To: <20161105090733.GT54029@kib.kiev.ua> References: <201611042049.uA4Knxcx019490@repo.freebsd.org> <20161105090733.GT54029@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/5/16 2:07 AM, Konstantin Belousov wrote: > On Fri, Nov 04, 2016 at 08:49:59PM +0000, Pedro F. Giffuni wrote: >> Author: pfg >> Date: Fri Nov 4 20:49:59 2016 >> New Revision: 308314 >> URL: https://svnweb.freebsd.org/changeset/base/308314 >> >> Log: >> sed(1): add LEGACY_BSDSED_COMPAT compile-time flag. >> >> In r297602, which included a __FreeBSD_version bump to 1100105, we changed >> sed 'i' and 'a' from discarding whitespaces to conform with what GNU and >> sysvish sed do. >> >> There are arguments in favor of keeping the old behavior but the new >> behavior is also useful for migration purposes. It seems important to at >> least consider the case of developers depending on the previous behavior, >> so add a CFLAG to enable the old behaviour. > If such legacy behavior appears to be useful or even important for > real-world scenarios, I think that an environment variable controlling > it is more practical and traditional than the recompilation. > +1
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6d9123fb-2b0a-c4a4-c584-d71874074d47>