Date: Mon, 30 Sep 2002 12:49:52 +0200 From: Sheldon Hearn <sheldonh@starjuice.net> To: David O'Brien <obrien@FreeBSD.org> Cc: Kris Kennaway <kris@obsecurity.org>, Mike Barcroft <mike@FreeBSD.org>, Eric Melville <eric@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/include Makefile getopt.h src/lib/libc/stdlib Makefile.inc getopt_long.3 getopt_long.c Message-ID: <20020930104952.GQ9330@starjuice.net> In-Reply-To: <20020929185747.GA85357@dragon.nuxi.com> References: <200209290414.g8T4EbCp043463@freefall.freebsd.org> <20020929044029.GA25349@dragon.nuxi.com> <20020929044137.GB14475@xor.obsecurity.org> <20020929010354.B622@espresso.q9media.com> <20020929051536.GA33717@xor.obsecurity.org> <20020929185747.GA85357@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On (2002/09/29 11:57), David O'Brien wrote: [... getopt_long support imported ...] > > > > NetBSD's pax uses this for longopt support in tar compatibility mode. > > > > > > Is this the extent to which it will be used in the base system? > > > > Well, I hope no-one has ideas about making it pervasive except for > > compatibility purposes. > > Even that is too nebulous. One might add all the '--' GNU ls options to > BSD ls for "compatibility purposes". Or add the GNU AWK '--' options, > especially since releng4's awk has them. Or du, df, etc.... Could you live with this policy: Tools in the base system may only use getopt_long to provide functionality offered in previously released versions of the base system. I think that as long as we constrain ourselves to using this for backward compatibility, we should be okay. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020930104952.GQ9330>