9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dmitry Golubovsky <golubovsky@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
Date: Mon, 26 Oct 2009 14:15:57 +0000	[thread overview]
Message-ID: <813b8c20-849c-4fae-b856-770824e4a038@u13g2000vbb.googlegroups.com> (raw)
In-Reply-To: <636733be-5009-4311-97ab-dc81634dbd06@p15g2000vbl.googlegroups.com>

On Oct 26, 9:21 am, 23h...@googlemail.com (hiro) wrote:
> > Since the purpose of ape is to emulate the environment configure is
> > expected to run in, and such mismatch has been found, it migh be
> > easier to fix ape than to convince maintaners of autoconf to fix on
> > their side...
>
> Why are you so sure they wouldn't fix it? Have you or has anybody you
> know tried something like this already?

Because even if they fix it in the current (or perhaps the nearest
future) version (in repos now) of autoconf this would not apply
retroactively to previous/current versions everyone has.

Besides, one thing (very long regexp to match all ASCII letters and
numbers in a CPP directive - see the thread on awk incompatibility) is
done on purpose: they specifically wanted to avoid character ranges
(perhaps wrt some locales where a-z range might also include letters
with diacritics, but this is only my guess). Regexp buffer length
limitation in Plan9 awk may be more fundamental problem.

Well, these problems arise only if one wants to have a port for Plan9
share the sources with upstream (hence to have common configure
scripts, Makefiles, tools, etc.)

If a fork-style port for Plan9 is considered then of course everything
may be adjusted properly (like configure is not needed at all because
there is only one
configuration, etc.).

Thanks.



  parent reply	other threads:[~2009-10-26 14:15 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
2009-10-26 10:19     ` Dmitry Golubovsky
2009-10-26 13:15       ` hiro
2009-10-26 14:15       ` Dmitry Golubovsky [this message]
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=813b8c20-849c-4fae-b856-770824e4a038@u13g2000vbb.googlegroups.com \
    --to=golubovsky@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).