The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com (Aharon Robbins)
Subject: [TUHS] licence of ditroff?
Date: Tue, 1 Feb 2005 11:01:38 +0200	[thread overview]
Message-ID: <200502010901.j1191cDT007818@skeeve.com> (raw)

> Date: Mon, 31 Jan 2005 17:50:26 +0000 (UTC)
> From: Thorsten Glaser <tg at 66h.42h.de>
> Subject: Re: [TUHS] licence of ditroff?
> To: Aharon Robbins <arnold at skeeve.com>
> Cc: martinwguy at yahoo.it, miros-discuss at 66h.42h.de, tuhs at minnie.tuhs.org
>
> Aharon Robbins dixit:
>
> >Instead of starting with 27 year old code, you'd be better
> >off taking the troff from http://www.swtch.com/plan9port.
>
> Thanks, that's a nice idea, but from what I experienced,
> the portability of recent AT&T/Bell/Lucent/whatever code
> is worse than the bugs in old code (eg. I could not get
> ksh93 to compile, something in there just dumped core;
> but then that's Unix, not Plan 9).

ksh93 is a different animal, from a different group, and problems
there are not surprising (sadly).

On the flip side, they do take bug reports seriously.

> >This is a port of many Plan 9 utilities to Unix.  The troff there
> >(a) has an explicit license that will probably do for the BSD people
>
> If it's the same licence as for 8c, then no, unfortunately.

I don't know.  It's worth double checking the current license; it
changed sometime in the past year or two.

The Plan 9 troff is certainly a descendant of the ditroff you
found, for whatever that's worth.

Arnold


             reply	other threads:[~2005-02-01  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01  9:01 Aharon Robbins [this message]
2005-02-01  9:28 ` Thorsten Glaser
  -- strict thread matches above, loose matches on Subject: below --
2005-01-31  9:39 Aharon Robbins
2005-01-31 17:50 ` Thorsten Glaser
2004-10-26 12:43 Thorsten Glaser

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=200502010901.j1191cDT007818@skeeve.com \
    --to=arnold@skeeve.com \
    /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).