From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <06a0be10-d05e-47f4-bebf-c9d9512de2b8@q14g2000vbi.googlegroups.com> Date: Fri, 23 Oct 2009 19:19:37 -0200 Message-ID: <32d987d50910231419p73446782j4f43fd5e121296ee@mail.gmail.com> From: "Federico G. Benavento" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Two suggestions for ape (was: egrep for Plan9) Topicbox-Message-UUID: 8f1ccfc4-ead5-11e9-9d60-3106f5b1d025 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 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