9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [GSOC 2013] Implement plan9 commands in Go, Goblin
Date: Tue, 30 Apr 2013 17:46:27 +0200	[thread overview]
Message-ID: <20130430154627.GA18540@polynum.com> (raw)
In-Reply-To: <CAEAzY39W3OO4-+SDbv7f96aCc1ayBm9wxY078UqpMssP=uaeDw@mail.gmail.com>

On Tue, Apr 30, 2013 at 05:26:50PM +0200, Aram H?v?rneanu wrote:
> > I don't see how they would benefit from being rewritten in go.
>
> Sometimes I need to deploy something written in rc(1) over a
> heterogenous Linux cluster,

This is in part Plan9 related. For kerTeX, simply because my compilation
framework was done this way, I use POSIX.2 utilities: sh(1) and make(1)
mainly. So, on Plan9, kerTeX compiles under APE.

But, despite POSIX being the one standard for systems, not everything is
really present everywhere, even on Unices (ed(1) is typically something
that is left out, while this is the only _line_ editor so the only
editor that should be here).

So I will have, to ensure that kerTeX runs everywhere, to provide some
core utilities. And I think I will switch from sh(1) (ksh or ash) to
rc(1) because rc(1) has regexp manipulations, and this is typically a
lot of what is done in the scripts (the a=$(echo $b | sed ...) is not
really efficient or beautiful).

So there may be a rc(1) base sys utilities set some day. (But if someone
does it before me, I will not be unhappy)

Because, using only C89 (or C99) is great. System(3) is standard C. But
the interpreter is neither guaranteed nor defined. If you have scripts
(and MetaPost has some for example; and kerTeX administration needs some
for the packages...)
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  parent reply	other threads:[~2013-04-30 15:46 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29 18:47 Alex-P. Natsios
2013-04-29 18:53 ` Alex-P. Natsios
2013-04-29 18:59   ` erik quanstrom
2013-04-29 19:11     ` Aram Hăvărneanu
2013-04-29 19:17       ` erik quanstrom
2013-04-29 19:27       ` arnold
2013-04-29 19:31         ` Aram Hăvărneanu
2013-04-29 19:33           ` Aram Hăvărneanu
2013-04-30  5:42       ` Jens Staal
2013-04-30  8:11         ` Bence Fábián
2013-04-30  9:00           ` Alex-P. Natsios
2013-04-30 15:26           ` Aram Hăvărneanu
2013-04-30 15:31             ` erik quanstrom
2013-04-30 15:41               ` Kurt H Maier
2013-04-30 15:44             ` Bence Fábián
2013-04-30 15:46             ` tlaronde [this message]
2013-04-30 18:18               ` Steve Simon
2013-04-30 21:03                 ` Steve Simon
2013-04-30 22:23                   ` suharik
2013-04-30 22:25                     ` erik quanstrom
2013-04-30 22:50                       ` suharik
2013-04-30 22:54                         ` erik quanstrom
2013-04-30 23:44                           ` suharik
2013-04-30 23:50                             ` Brantley Coile
2013-05-01  0:56                             ` erik quanstrom
2013-05-01  5:05                               ` Matthew Veety
2013-05-03 13:31                   ` Yaroslav
2013-04-30 21:03                 ` Paul Patience
2013-05-01  6:49                 ` tlaronde
2013-04-30 12:28         ` erik quanstrom
2013-04-29 19:00   ` Aram Hăvărneanu
2013-04-29 19:52     ` andrey mirtchovski
2013-04-29 19:58       ` erik quanstrom
2013-04-29 20:22         ` andrey mirtchovski
2013-04-29 20:00       ` Aram Hăvărneanu
2013-04-29 20:02         ` erik quanstrom
2013-04-29 22:45       ` Kurt H Maier
2013-04-29 21:59         ` andrey mirtchovski
2013-05-01  9:30 ` mortdeus
2013-05-01 10:58 ` mortdeus
2013-05-01 11:13   ` Alex-P. Natsios
2013-05-01 13:38 ` mortdeus
2013-05-02  0:02 ` erik quanstrom
2013-05-02  0:11   ` andrey mirtchovski
2013-05-02  1:01     ` Devon H. O'Dell
2013-05-02  1:06       ` erik quanstrom
2013-05-02  1:57     ` Lyndon Nerenberg
2013-05-02  3:34     ` Matthew Veety

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=20130430154627.GA18540@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).