From: "Federico G. Benavento" <benavento@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 19:19:37 -0200 [thread overview]
Message-ID: <32d987d50910231419p73446782j4f43fd5e121296ee@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSI.4.64.0910230816370.23231@malasada.lava.net>
http://plan9.bell-labs.com/sources/contrib/fgb/rc/config
hacks configure and mostly gets it going
for egrep and fgrep
aux/stub /bin/egrep
bind /bin/grep /bin/egrep
On Fri, Oct 23, 2009 at 4:18 PM, Tim Newsham <newsham@lava.net> wrote:
>> Jason: I understand your reasoning. However if two small fixes would
>> unblock execution of many projects' configure on Plan9 IMHO they are
>> worth making; they won't break anything.
>
> What if you just made a command "gnuconfig" which rewrote the
> configure script, fixing the minor defects, and ran the result?
> Or bound in a dummy "ls" and "egrep" before executing the real
> configure script?
> Lets keep the infection contained.
>
>> Thanks.
>> Dmitry
>
> Tim Newsham
> http://www.thenewsh.com/~newsham/
>
>
--
Federico G. Benavento
next prev parent reply other threads:[~2009-10-23 21:19 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
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 [this message]
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=32d987d50910231419p73446782j4f43fd5e121296ee@mail.gmail.com \
--to=benavento@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).