From: Ulrich Mueller <ulm@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New category: dev-doc (?)
Date: Sun, 07 Jan 2024 17:58:52 +0100 [thread overview]
Message-ID: <uttnpaxmb@gentoo.org> (raw)
In-Reply-To: <f48a14d3ec9b19f769251bfb384eff0420a328e2.camel@gentoo.org> (=?utf-8?Q?=22Micha=C5=82_G=C3=B3rny=22's?= message of "Sun, 07 Jan 2024 17:39:11 +0100")
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
>>>>> On Sun, 07 Jan 2024, Michał Górny wrote:
> Here's another idea, a new dev-doc category (though I suppose we could
> try to find a better name), dedicated to:
> Tools to generate, convert, view and process documentation.
> This is notably meant to move software out of app-doc/ which is
> specifically dedicated to "documentation collections". Candidates:
> app-doc/NaturalDocs
> app-doc/doxygen
> app-doc/halibut
> app-doc/psmark
> app-doc/xmltoman
> app-doc/zeal
> app-text/mandoc
> app-text/texi2html
> app-text/xchm
> app-text/xml2rfc
> app-text/xmlto
I cannot really see a delineation between app-text and app-doc.
For example, packages like psmark, xmlto, or even texi2html are general
format manipulation/conversion tools and IMHO app-text is the right
category for them. Also, why would you keep pandoc and manpager in
app-text but move xmlto and mandoc out of it?
> dev-util/gi-docgen
> dev-util/gtk-doc
> dev-util/source-highlight
> sys-apps/man-db
> sys-apps/texinfo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2024-01-07 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 16:39 [gentoo-dev] [RFC] New category: dev-doc (?) Michał Górny
2024-01-07 16:58 ` Ulrich Mueller [this message]
2024-01-07 17:03 ` Ulrich Mueller
2024-01-07 18:26 ` Michał Górny
2024-01-08 6:51 ` Ulrich Mueller
2024-01-08 13:44 ` Michał Górny
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=uttnpaxmb@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@gentoo.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