From owner-freebsd-ports Wed Nov 11 11:03:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20746 for freebsd-ports-outgoing; Wed, 11 Nov 1998 11:03:49 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20708 for ; Wed, 11 Nov 1998 11:03:42 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA095030847; Wed, 11 Nov 1998 14:00:47 -0500 Date: Wed, 11 Nov 1998 14:00:47 -0500 (EST) From: Bill Fumerola To: Dom Mitchell Cc: ports@FreeBSD.ORG Subject: Re: GNU getopt In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 11 Nov 1998, Dom Mitchell wrote: > What a pain, it seemed like such a useful little tool to start with. I > shall mail the author and ask him to include those files with the > distribution, because I'm sure that FreeBSD isn't the only Unix which > has problems with getopt_long. In a recent port I did (but haven't committed it yet) the author provided a define to disable it. The only thing you lost by not having getopt_long, was long options, not the whole command line interface, which is what sometimes happens with these apps. Perhaps someone from -hackers or something could comment on how we could have a getopt_long that could be implemented in these ports. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message