From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Cc: Thomas Klausner <wiz@NetBSD.org>
Subject: Re: [jperkin@netbsd.org: CVS commit: pkgsrc/textproc/mdocml]
Date: Mon, 16 Sep 2013 00:26:38 +0200 [thread overview]
Message-ID: <20130915222638.GN4706@iris.usta.de> (raw)
In-Reply-To: <20130915215048.GF24806@danbala.tuwien.ac.at>
Hi Thomas,
Thomas Klausner wrote on Sun, Sep 15, 2013 at 11:50:48PM +0200:
> Just to make sure it's clear -- this is only for pkgsrc.
> NetBSD's base contains mdocml (used for man pages by default)
Oh really! When did you switch to using mandoc(1) as the system's
manual page formatter? I didn't even notice you switched...
[...]
> To fill in the picture: NetBSD base installs all mandoc man pages in
> section 7 as mandoc_foo.7, and of the binaries only mandoc itself.
Oh, i see.
> If NetBSD ever gets rid of groff, they might be renamed back to their
> default names, but as long as we have distribution/setup notes in
> roff, this won't happen anytime soon.
>
> Btw, what does OpenBSD do with the installation notes, or were they
> rewritten in something else but roff?
Not sure what you are talking about, maybe something like this?
http://www.openbsd.org/cgi-bin/cvsweb/src/distrib/notes/INSTALL
In any case, no plain roff code remains in OpenBSD, and all roff
macro code is mdoc(7), man(7), and eqn(7) and can be handled
by mandoc(1).
> So there is no mandoc package in ports?
No, in OpenBSD, it is very unusual to have software in ports
that is already available in the base system, with few exceptions.
- fvwm is old but stable in base, fvwm in ports is GPL
- httpd is old and audited in base, apache-httpd in ports has a bad license
There may be a few others, but in general, if the version in base is
up to date and maintained, there won't be a port.
>> I agree that calling our manual "roff(7)" was presumptuous, and that
>> mandoc-roff(7) is better. If Kristaps explicitly agrees i might
>> consider renaming the file in the bsd.lv repo as well. Probably,
>> i would first ask for opinions in OpenBSD as well because keeping
>> things in sync would be nicer.
> I guess more pages would need to be renamed to be consistent.
> I'm not sure what to do here, so I just sent it as a FYI.
OK, so let's leave it as it is for now and avoid change
that would verge change for change's sake.
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2013-09-15 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 11:03 Thomas Klausner
2013-09-15 12:31 ` Ingo Schwarze
2013-09-15 21:50 ` Thomas Klausner
2013-09-15 22:26 ` Ingo Schwarze [this message]
2013-09-17 20:43 ` Thomas Klausner
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=20130915222638.GN4706@iris.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mdocml.bsd.lv \
--cc=wiz@NetBSD.org \
/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).