9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] graphviz
Date: Thu,  4 Mar 2004 00:22:42 +0400	[thread overview]
Message-ID: <200403032022.i23KMgR3053241@adat.davidashen.net> (raw)
In-Reply-To: <88a386cc922f703f432afb566ed42a38@plan9.ucalgary.ca>

> > It will take longer, and does not make much sense for graphviz,
> > I am afraid.
>
> it doesn't makes sense to rewrite it into something more sensible?
>
> puzzled.

Right now, graphviz is distributed by AT&T with autoconf's configure
script, and (with few modifications to the result) it is used 
to compile it under APE.  Changes to the source code are localized
and the patches will hopefully be applicable to new releases too.

Looking at the diff, I think it would make sense to incorporate the
changes into the main distribution.

Removing vowels from make would be a good excercise, but would 
require continuous maintenance of the port. Unless a different
environment is written around the same algorithmic core to fit
into Plan9 environment, it does not make much sense, I think.

It's just a tool to draw graphs. It will not begin to draw
better graphs when compiled with mk instead of make.

David Tolpin


  reply	other threads:[~2004-03-03 20:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 19:45 David Tolpin
2004-03-03 19:59 ` andrey mirtchovski
2004-03-03 20:08   ` David Tolpin
2004-03-03 20:15     ` andrey mirtchovski
2004-03-03 20:22       ` David Tolpin [this message]
2004-03-03 21:00         ` splite
2004-03-03 21:08           ` David Tolpin
2004-03-03 21:42             ` splite
2004-03-04  9:59               ` Robin KAY
2004-03-03 22:29     ` boyd, rounin
2007-06-11  6:43 [9fans] Graphviz Lyndon Nerenberg
2007-06-11  7:02 ` Gabriel Diaz

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=200403032022.i23KMgR3053241@adat.davidashen.net \
    --to=dvd@davidashen.net \
    --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).