From owner-freebsd-standards Sun Oct 27 10: 4:11 2002 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7B1037B4A4 for ; Sun, 27 Oct 2002 10:04:07 -0800 (PST) Received: from thuvia.demon.co.uk (thuvia.demon.co.uk [193.237.34.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 697E843E3B for ; Sun, 27 Oct 2002 10:04:06 -0800 (PST) (envelope-from mark@thuvia.demon.co.uk) Received: from dotar.thuvia.org (dotar.thuvia.org [10.0.0.4]) by phaidor.thuvia.org (8.12.3/8.12.3) with ESMTP id g9RI44cF056961; Sun, 27 Oct 2002 18:04:04 GMT (envelope-from mark@thuvia.demon.co.uk) Received: from dotar.thuvia.org (localhost [IPv6:::1]) by dotar.thuvia.org (8.12.6/8.12.6) with ESMTP id g9RI44H5039770; Sun, 27 Oct 2002 18:04:04 GMT (envelope-from mark@dotar.thuvia.org) Received: (from mark@localhost) by dotar.thuvia.org (8.12.6/8.12.6/Submit) id g9RI433K039769; Sun, 27 Oct 2002 18:04:03 GMT Date: Sun, 27 Oct 2002 18:04:03 GMT From: Mark Valentine Message-Id: <200210271804.g9RI433K039769@dotar.thuvia.org> In-Reply-To: <200210271724.g9RHObQ2031513@khavrinen.lcs.mit.edu> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Garrett Wollman Subject: Re: Why I am opposed to a Standards Ghetto Cc: standards@freebsd.org Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: Garrett Wollman > Date: Sun 27 Oct, 2002 > Subject: Re: Why I am opposed to a Standards Ghetto > If we were going to go down this road, the only implementation I could > reasonably support would be an environment variable which downgraded > from standard to ``like it was in FreeBSD 4.x'' -- with the default > being standards-compliant. The problem here is that this requires end user action to get "broken" software working again, and it's still not clear what that action is. Consider my example situation with an end user unfamiliar with shell programming and with a "broken" and no longer supported product. It's going to take a *lot* of head scratching to figure out he has to set this environment variable. Even then, where does he set it? In his .profile? That breaks any software he runs which assumes the environment is Standards compliant (e.g. stuff written for FreeBSD 5.0). And it won't help parts of the product started from /etc/rc or from cron(1). > Perhaps something like this: > > - Deprecate EXPR_COMPAT. > - Define a new standard environment variable, _FreeBSD_4_COMPAT, the > value of which can be either the empty string or a list of programs to > be affected. > - Add a new library routine, int check_utility_compat(const char > *utility), which centralizes checking for this environment variable. > - Update expr(1) and sort(1) to be the first clients. This may be a little neater than the current implementation, but it's effectively functionally equivalent - just uses another environment variable - and doesn't actually help solve the problem. Sorry. Cheers, Mark. -- Mark Valentine, Thuvia Labs "Tigers will do ANYTHING for a tuna fish sandwich." Mark Valentine uses "We're kind of stupid that way." *munch* *munch* and endorses FreeBSD -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message