9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jason Catena <jason.catena@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
Date: Fri, 23 Oct 2009 09:06:45 -0500	[thread overview]
Message-ID: <d50d7d460910230706j58181763n409b237ea4c23fb2@mail.gmail.com> (raw)
In-Reply-To: <bcba51a0910230343w2563a6fehbcd094a7eb05b38f@mail.gmail.com>

Dimitry wrote:
> I have two suggestions for ape minor additions arising from my recent
> attempts to run configure scripts on Plan9
>
> These things are needed by autoconf.
>
> Looks like these
> things are hardwired in the autoconf macro library.

Since autoconf should deal with "any" unixy environment in which it
finds itself (that's supposed to be what it does for a living),
shouldn't it be patched to deal with a lack of POSIX grep's -E and
POSIX ls' -i?  In general, as a porting tool, it should not make
demands on the host system for the presence of egrep, or options are
defined by GNU tools (or even POSIX).  Making such demands places
arbitrary limits on how portable the gnu tools are, or any tools using
autoconf.  (Given the FSF's philosophy, this may be intentional.)

POSIX-ls has 23 options to Plan9-ls' 12.  I can't imagine that we'd
add in all the remaining options of ls just because some program or
another uses them.

egrep has 42 options to POSIX-grep's 11 options to Plan9-grep's
different 11.  I can't imagine that we'd change around the meaning of
the 11 options to suit POSIX, let alone add in the extra ones of
egrep.

Take all this with a grain of salt, because I don't speak for any
distribution. :)

> Dimitry Golubovsky

Jason Catena



  reply	other threads:[~2009-10-23 14:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23 10:43 Dimitry Golubovsky
2009-10-23 14:06 ` Jason Catena [this message]
2009-10-23 14:12   ` Charles Forsyth
2009-10-23 15:06     ` W B Hacker
2009-10-23 15:38     ` Federico G. Benavento
2009-10-23 15:54   ` Dmitry Golubovsky
2009-10-23 16:08     ` Jason Catena
2009-10-23 18:18     ` Tim Newsham
2009-10-23 18:58       ` Jason Catena
2009-10-23 21:19       ` Federico G. Benavento
2009-10-26 10:19     ` Dmitry Golubovsky
2009-10-26 13:15       ` hiro
2009-10-26 14:15       ` Dmitry Golubovsky
2009-10-26 15:06         ` [9fans] Two suggestions for ape W B Hacker
     [not found]     ` <636733be-5009-4311-97ab-dc81634dbd06@p15g2000vbl.googlegroups.co>
2009-10-26 20:10       ` [9fans] Two suggestions for ape (was: egrep for Plan9) erik quanstrom
2009-10-27 16:10         ` Anthony Sorace
2009-10-27 16:16           ` erik quanstrom
2009-10-27 16:25             ` ron minnich
2009-10-27 16:37               ` erik quanstrom
2009-10-27 17:56                 ` tlaronde
2009-10-27 21:43                   ` Tim Newsham
2009-10-27 23:14                     ` Francisco J Ballesteros
2009-10-28  0:23                   ` Dave Eckhardt
2009-10-28  9:45                     ` tlaronde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d50d7d460910230706j58181763n409b237ea4c23fb2@mail.gmail.com \
    --to=jason.catena@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).