Date: Tue, 24 Sep 2002 18:24:35 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Garrett Wollman <wollman@lcs.mit.edu>, Bill Fenner <fenner@research.att.com> Cc: current@FreeBSD.ORG Subject: Re: Who broke sort(1) ? Message-ID: <p05111702b9b69456fc23@[128.113.24.47]> In-Reply-To: <200209242202.g8OM25P1091340@khavrinen.lcs.mit.edu> References: <20020923122935.A6108@dilbert.robbins.dropbear.id.au> <20020924203011.5EF752A7D6@canning.wemm.org> <200209242101.g8OL1TVd090894@khavrinen.lcs.mit.edu> <200209242109.OAA26770@windsor.research.att.com> <200209242202.g8OM25P1091340@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At 6:02 PM -0400 9/24/02, Garrett Wollman wrote: ><<On Tue, 24 Sep 2002, Bill Fenner <fenner@research.att.com> said: > > > When's the first time the FreeBSD sort(1) man page mentioned that > > this syntax was deprecated? Can we at least start from there? > >It does not appear to have ever been properly documented. > >I don't object to maintaining backwards compatibility for a few more >releases (even if the application writers are the ones at fault), >since many more people read the manual pages than read the Standard. >However, I would point out that this isn't the first time we broke a >traditional syntax in favor of reducing restrictions on argument >names: see the recent history of chown(8). In the case of 'sort', I would rather see us ease into the change a bit more. We already have enough going on with 5.0-current that we don't need the extra excitement of this particular change. I can readily live with the fact that 5.0-release will not be 100% posix compliant. I know I have all kinds of scripts squirreled away which have 'sort +n' commands in them, and I have zero real files that are named +n. This change gives me nothing but broken scripts, and I would rather see us have an "almost posix" sort, and with the option to set an environment variable to remove support for +N. That way, the people who *want* to debug a bunch of scripts can set that environment variable, instead of forcing the rest of us to run around setting an environment variable to protect us from broken scripts. In some sense I don't mind the change, but I really think we are now past the point where we can keep throwing incompatible changes into 5.0-release. We have enough broken ports on 5.0-current, we do not need more incompatible changes to break even more ports to give us even more work to do. Just my 2 cents... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05111702b9b69456fc23>