From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Easy stating of newer files on Plan9
Date: Sat, 14 May 2011 23:25:24 +0200 [thread overview]
Message-ID: <20110514212524.GA28019@polynum.com> (raw)
Hello,
I have finished to add MetaPost to kerTeX and I'm testing and polishing.
My aim is to have something strictly C89.
There is one utility used by MetaPost scripts: a binary "newer" using
POSIX (sys/stat.h) mainly because if on POSIX compliant systems one can
use find(1) with "-cnewer", Plan9 has not find(1).
3 options:
1) Let this POSIX exception "newer";
2) Drop this optimization (AFAIK) in the scripts;
3) Patch the scripts with "find..." for not Plan9, and
some ls, cut, whatever line for Plan9 just for consistency.
My preference is 3).
What would be the prefered way using utilities available on Plan9 (and
accessible for ape/sh) since the scripts are Bourne shell ones.
TIA
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next reply other threads:[~2011-05-14 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 21:25 tlaronde [this message]
2011-05-14 21:55 ` Anthony Martin
2011-05-15 6:52 ` 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=20110514212524.GA28019@polynum.com \
--to=tlaronde@polynum.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).