From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: patch/list applied/ape-dumb-autohell-fixes
Date: Mon, 13 Feb 2006 12:29:07 -0500 [thread overview]
Message-ID: <ee9e417a0602130929h21838c9epd093c592a7e75988@mail.gmail.com> (raw)
In-Reply-To: <6e0a93d2952defd6f4258eab2dc26322@cat-v.org>
> % grep '\$srcdir/configure' SDL-1.2.9/configure
> set X `ls -Lt $srcdir/configure conftest.file 2> /dev/null`
> set X `ls -t $srcdir/configure conftest.file`
> if test "$*" != "X $srcdir/configure conftest.file" \
> && test "$*" != "X conftest.file $srcdir/configure"; then
>
> ($srcdir is '.')
I think this is just a bug in the Plan 9 ls. It uses
cleanname as a crutch to avoid doubling / in some names,
but that makes it somewhat inconsistent. For example:
cd /sys/src/cmd
ls . | grep ls.c
ls ./ls.c
produces two different lines.
I put a new ls.c on sources that is a bit more consistent
and should work better in the above script.
> I don't like the idea of forking stuff, but in the end it's going to be the only
> way if APE is going to emulate all the lunix crap well enough to be useful.
Says you. I think having wrappers (as we do for yacc and ar)
is a much better long-term approach. Then there's still only
one program providing the core functionality.
Also, just to be clear, APE is the Ansi/Posix Environment,
not the "Any random craP that linux does Environment".
The configure scripts that autoconf writes are written to
the intersection of pretty much every Unix out there,
so if there's something they expect (like mkdir -p or ls -L)
then it's worth adding. But compatibility with GNU/Linux
is *not* the goal.
> > I do not believe that cleanname needs to come out.
> > I used to run ./configure scripts all the time without
> > needing to touch ls.
> Maybe it's a recent "improvement" to the auto*hell world.
I don't really see the point to incendiary names like auto*hell.
Are you just trying to make yourself feel better?
Russ
next prev parent reply other threads:[~2006-02-13 17:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7c5561c3fea402ccac05d5762e3d2aa7@plan9.bell-labs.com>
2006-02-13 16:17 ` uriel
2006-02-13 17:29 ` Russ Cox [this message]
2006-02-13 19:46 ` uriel
2006-02-13 15:19 ` Russ Cox
2006-02-13 19:51 ` Lyndon Nerenberg
2006-02-13 20:23 ` Ronald G Minnich
2006-02-13 20:44 ` Lyndon Nerenberg
2006-02-13 22:54 ` Ronald G Minnich
2006-02-14 15:57 ` David Leimbach
2006-02-13 20:21 ` Ronald G Minnich
2006-02-13 20:47 ` Steve Simon
2006-02-13 20:55 ` Paul Lalonde
2006-02-13 20:58 ` Steve Simon
2006-02-13 23:02 ` Ronald G Minnich
2006-02-13 21:07 ` andrey mirtchovski
2006-02-14 0:39 ` Latchesar Ionkov
2006-02-14 0:41 ` Paul Lalonde
2006-02-14 0:59 ` Latchesar Ionkov
2006-02-14 0:50 ` Joel Salomon
2006-02-14 0:53 ` Joel Salomon
2006-02-14 1:04 ` Latchesar Ionkov
2006-02-14 1:12 ` Joel Salomon
2006-02-14 9:47 ` Charles Forsyth
2006-02-14 11:37 ` Brantley Coile
2006-02-14 14:43 ` Ronald G Minnich
2006-02-14 10:12 ` Russ Cox
2006-02-14 15:10 ` Ronald G Minnich
2006-02-14 15:53 ` David Leimbach
2006-02-14 1:31 quanstro
2006-02-15 0:53 quanstro
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=ee9e417a0602130929h21838c9epd093c592a7e75988@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).