From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Another "craft" discussion topic - mindless tool proliferation
Date: Thu, 21 Sep 2017 20:25:30 -0600 [thread overview]
Message-ID: <CANCZdfotevSHGzvtch0MNSYbaZDPbTeQ=j7YQFyp0nCE1P7QRQ@mail.gmail.com> (raw)
In-Reply-To: <20170922005053.GN25650@mcvoy.com>
On Thu, Sep 21, 2017 at 6:50 PM, Larry McVoy <lm at mcvoy.com> wrote:
> On Thu, Sep 21, 2017 at 05:39:25PM -0700, Lyndon Nerenberg wrote:
> >
> > > On Sep 21, 2017, at 5:38 PM, Larry McVoy <lm at mcvoy.com> wrote:
> > >
> > > And removing roff from BSD is gonna make me mad. I'm about to start
> > > doing some work on BSD so maybe I'll make some noise. Or did the *roff
> > > tools stick around?
> >
> > Apparently they are all rewriting nroff into something called mandoc.
>
> Oh, brother. Like the BSD Makefile crap. "Better" but nobody else uses
> it.
>
mandoc is a restricted set of troff that implements the traditional mandoc
troff macros. So the conversion was just tweaking a few edge cases. And all
the BSDs are using it these days.
> Somebody needs a clue stick. Might be them, might be me, but it's needed
>
It sure beats the crazy language gnu make has become. FreeBSD has used
variations on pmake the entire life of the project, though FreeBSD's
version diverged somewhat until we abandoned the divergence to bring back
the evolved pmake from NetBSD.
Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170921/2e02ffe8/attachment.html>
next prev parent reply other threads:[~2017-09-22 2:25 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 17:01 Jon Steinhart
2017-09-19 17:05 ` Steve Nickolas
2017-09-19 20:31 ` Pete Turnbull
2017-09-19 20:37 ` Warner Losh
2017-09-19 23:35 ` Theodore Ts'o
2017-09-20 0:47 ` Lyndon Nerenberg
2017-09-20 1:02 ` Larry McVoy
2017-09-20 1:09 ` Lyndon Nerenberg
2017-09-20 1:13 ` Larry McVoy
2017-09-20 1:22 ` Larry McVoy
2017-09-20 2:01 ` Larry McVoy
2017-09-20 2:34 ` Bakul Shah
2017-09-20 2:47 ` Larry McVoy
2017-09-20 6:18 ` Bakul Shah
2017-09-20 4:35 ` Grant Taylor
2017-09-20 5:54 ` Ian Zimmerman
2017-09-24 23:03 ` Ralph Corderoy
2017-09-24 23:35 ` Bakul Shah
2017-09-20 16:49 ` Steffen Nurpmeso
2017-09-20 4:29 ` Grant Taylor
2017-09-20 6:43 ` Peter Jeremy
2017-09-20 8:25 ` Bakul Shah
2017-09-20 9:12 ` Steve Nickolas
2017-09-20 9:34 ` Bakul Shah
2017-09-20 16:48 ` Steffen Nurpmeso
2017-09-20 2:07 ` Theodore Ts'o
2017-09-24 22:58 ` Ralph Corderoy
2017-09-20 4:26 ` Grant Taylor
2017-09-20 16:45 ` Steffen Nurpmeso
2017-09-21 17:33 ` Tony Finch
2017-09-21 18:39 ` Steffen Nurpmeso
2017-09-22 0:02 ` Greg 'groggy' Lehey
2017-09-22 0:30 ` Lyndon Nerenberg
2017-09-22 0:38 ` Larry McVoy
2017-09-22 0:39 ` Lyndon Nerenberg
2017-09-22 0:50 ` Larry McVoy
2017-09-22 1:01 ` Lyndon Nerenberg
2017-09-22 1:08 ` Larry McVoy
2017-09-22 20:09 ` [TUHS] remaking make (Re: " Bakul Shah
2017-09-22 2:25 ` Warner Losh [this message]
2017-09-22 3:26 ` [TUHS] " Greg 'groggy' Lehey
2017-09-22 4:09 ` ron minnich
2017-09-22 2:20 ` Warner Losh
2017-09-22 0:36 ` Larry McVoy
2017-09-22 0:40 ` Lyndon Nerenberg
2017-09-22 1:53 ` Michael Parson
2017-09-22 3:25 ` Grant Taylor
2017-09-20 6:20 ` Lars Brinkhoff
2017-09-20 16:39 ` Steffen Nurpmeso
2017-09-24 22:54 ` Ralph Corderoy
2017-09-25 0:16 ` Steve Johnson
2017-09-25 11:30 ` Ralph Corderoy
2017-09-20 18:15 ` Clem Cole
2017-09-20 18:35 ` Jon Steinhart
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='CANCZdfotevSHGzvtch0MNSYbaZDPbTeQ=j7YQFyp0nCE1P7QRQ@mail.gmail.com' \
--to=imp@bsdimp.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).