9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Luther Huffman, Jr. lutherh@infinet.com
Subject: the licence
Date: Thu, 22 Feb 1996 21:31:07 -0500	[thread overview]
Message-ID: <19960223023107.TnQhCFv7se-ULy89XO4ERBGT_efiI__0fMfcQHRybjk@z> (raw)

On Thu, 22 Feb 1996 19:08:12 -0500, you wrote:

Generous I think might be stretching it. Although I meant this as a
joke, the agreement *could* be onerous. But, as they say in legal
circles, the real meaning of an agreement is in the intent. And the
intent of the Plan 9 people is to provide source code to those who are
interested. They've done a tremendous job at this, second to no one.
   Certainly I would agree with you that I like the Plan 9 setup.
That's why I've invested a great deal of resources and effort into
supporting it.
   On a different note, bless your heart, I thought I was the only one
on earth to loath and despise Metaconfig, Configure and all of their
evil spawn. I'm the porter for Plan 9 Perl (the new object oriented
one). 95% of the perl-porters are in love with that blasted Configure.
It is the bane of my existence. The Perl configure script pure and
simply won't run under Plan 9. That means I have to edit a 30k,
ill-commented config.h header file by hand. I have no human-readable
makefile to document dependencies.
   Perl 5.002 is ready to hit the streets next week. Roughly 50 bugs
per day are being posted to the perl-porters mailing list. You may be
interested to know that perhaps 5 per week are core release bugs. The
rest deal with Configure, setup, and the like. 
   On the other hand, I'm also working on a Haskell compiler for Plan
9 (with luck it may be part of Brazil; I'm still working on buttering
up Howard Trickey, who has sold his soul to Standard ML). It currently
runs under NetBSD, uses plain old makefiles and no configure scripts.
Even though I'll have to completely rewrite the code generator and
cross-compile from an entirely different platform because it
bootstraps itself, the overall effort is much easier than the Perl
interpreter. Trying to create one distribution that can compile on all
platforms escalates the complexity to the point that the code is
unmanageable.

By the way, late tonight the Inferno team will post info about their
work on the home page late tonight, or so my mole on the team has
informed me.
>i was surprised by this comment, although i've heard it before.
>i suspect it is fast becoming a popular misconception.
>the Plan 9 licence certainly isn't a free for all,
>but seems to me to be a reasonable attempt at protecting each party's interests in
>an agreeable, equitable, and even generous manner.
>
>frankly, compared to the FSF offering, i'm willing to pay for Plan 9
>and even give up kittens, if i owned them, so as not to have to invoke one of
>those wretched `configure' scripts ever again.
>







             reply	other threads:[~1996-02-23  2:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-02-23  2:31 Luther [this message]
  -- strict thread matches above, loose matches on Subject: below --
1996-02-23 17:06 pete.fenelon
1996-02-23 15:28 Arnold
1996-02-23 14:05 Boyd
1996-02-23 14:00 Boyd
1996-02-23  9:06 forsyth
1996-02-23  8:41 forsyth
1996-02-23  8:25 forsyth
1996-02-23  8:17 Nigel
1996-02-23  4:45 Luther
1996-02-23  4:18 Greg
1996-02-23  1:20 Paul
1996-02-23  0:08 forsyth

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=19960223023107.TnQhCFv7se-ULy89XO4ERBGT_efiI__0fMfcQHRybjk@z \
    --to=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).