discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Thomas Klausner <wiz@NetBSD.org>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mdocml.bsd.lv
Subject: Re: [jperkin@netbsd.org: CVS commit: pkgsrc/textproc/mdocml]
Date: Sun, 15 Sep 2013 23:50:48 +0200	[thread overview]
Message-ID: <20130915215048.GF24806@danbala.tuwien.ac.at> (raw)
In-Reply-To: <20130915123135.GA4706@iris.usta.de>

Hi Ingo!

On Sun, Sep 15, 2013 at 02:31:35PM +0200, Ingo Schwarze wrote:
> > Date: Thu, 12 Sep 2013 10:33:29 +0000
> > From: Jonathan Perkin <jperkin@netbsd.org>
> > To: pkgsrc-changes@NetBSD.org
> > Subject: CVS commit: pkgsrc/textproc/mdocml
> [...]
> > Log Message:
> > Rename preconv and roff.7 to have a 'mandoc-' prefix.  This removes the
> > conflicts with textproc/groff and allows both packages to co-exist,
> > paving the way for mdocml to be used in the tools infrastructure as an
> > nroff replacement.
> 
> I see why this makes sense for NetBSD.

Just to make sure it's clear -- this is only for pkgsrc. NetBSD's base
contains mdocml (used for man pages by default) and parts of groff
(for roff sources). The best-fitting comparison would be to OpenBSD
ports.

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.

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?

> In OpenBSD, we don't have these conflicts.
> OpenBSD doesn't provide preconv(1) at all, neither the program
> nor the manual.
> While the roff.7 from mandoc lives in /usr/share/man/,
> the roff.7 from groff lives in /usr/local/man/,
> so there is no conflict either.

So there is no mandoc package in ports? Then OpenBSD doesn't have this
issue, I agree.

> 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.

> So far, i didn't look at preconv(1) at all and hardly know what
> it is doing.  Maybe at some point i will look at it, but before
> that, i feel quite reluctant to touch it at all.

This was the first time I noticed this program too :)

> I used the ooportunity to check out a copy of pkgsrc/textproc/mdocml
> and look around a bit.

Thanks for the comments on the package. I've improved both COMMENT and
DESCR using your words.

Thanks for your suggestions!
 Thomas
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2013-09-15 21:50 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 [this message]
2013-09-15 22:26     ` Ingo Schwarze
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=20130915215048.GF24806@danbala.tuwien.ac.at \
    --to=wiz@netbsd.org \
    --cc=discuss@mdocml.bsd.lv \
    --cc=schwarze@usta.de \
    /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).