From: Raf Czlonka <rczlonka@gmail.com>
To: tech@mandoc.bsd.lv
Subject: Re: [PATCH] ports.html - update operating systems table
Date: Fri, 11 Nov 2022 12:51:15 +0000 [thread overview]
Message-ID: <Y25FQxTLREeMVNZV@gmail.com> (raw)
In-Reply-To: <Y2z/3bWBEv+BsBaq@www.stare.cz>
Hi Jan,
On Thu, Nov 10, 2022 at 01:42:53PM GMT, Jan Stary wrote:
> On Nov 10 12:30:01, rczlonka@gmail.com wrote:
> > Newly released macOS Ventura (version 13) comes with mandoc 1.14.5 included.
>
> If you already have that installed, can you please try
> running that version of mandoc on groffer.1?
>
> /System/Volumes/Data/Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/usr/share/man/man1/groffer.1
>
> In my previous attempts to replace the system man with mandoc,
> it always choked on that.
Looks OK at a quick glance.
> (A message in arm@openbsd.org (I think) warned that macOS 13
> installs some new firmware that creates problems for the
> multibooting OpenBSD on M1 macbooks, so I'm still on macOS 12.)
This one's an Intel Mac which only runs macOS.
> > I couldn't find any official release information and the sources aren't
> > available on https://opensource.apple.com/releases/ yet so no direct
> > links yet.
>
> They seem to gradually replace part of the system with BSD stuff:
> pf, mdoc(5) manpages, now mandoc itself; that's good news.
Yes, Apple's GPL purge has been in motion for a while now.
Regards,
Raf
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
prev parent reply other threads:[~2022-11-11 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 12:30 Raf Czlonka
2022-11-10 13:42 ` Jan Stary
2022-11-11 12:51 ` Raf Czlonka [this message]
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=Y25FQxTLREeMVNZV@gmail.com \
--to=rczlonka@gmail.com \
--cc=tech@mandoc.bsd.lv \
/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).