public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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: Mon, 08 Jan 2024 07:51:56 +0100	[thread overview]
Message-ID: <ule90b9mb@gentoo.org> (raw)
In-Reply-To: <fb5594c7a3cc52509ab486b81ee2f4c616c380f4.camel@gentoo.org> (=?utf-8?Q?=22Micha=C5=82_G=C3=B3rny=22's?= message of "Sun, 07 Jan 2024 19:26:36 +0100")

[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]

>>>>> On Sun, 07 Jan 2024, Michał Górny wrote:

> On Sun, 2024-01-07 at 17:58 +0100, Ulrich Mueller wrote:
>> I cannot really see a delineation between app-text and [dev]-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?

> It's a bit blurry.  My original idea was to keep app-text/ for general-
> purpose text tools (like text editors), while make dev-doc/ focused on
> formats specific to documentation (like code documentation, manpages).

We already have app-editors for text editors. For the rest, it seems
very blurry indeed and would leave us with (IMHO too many) borderline
cases.

You certainly have a point that document processing tools are misplaced
in app-doc. Maybe just move them to app-text, which would be a more
minimal change?

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

  reply	other threads:[~2024-01-08  6:52 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
2024-01-07 17:03   ` Ulrich Mueller
2024-01-07 18:26   ` Michał Górny
2024-01-08  6:51     ` Ulrich Mueller [this message]
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=ule90b9mb@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