From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New category: dev-doc (?)
Date: Mon, 08 Jan 2024 14:44:22 +0100 [thread overview]
Message-ID: <c9df83725128d5470d60750be7a102edaf6b50cb.camel@gentoo.org> (raw)
In-Reply-To: <ule90b9mb@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
On Mon, 2024-01-08 at 07:51 +0100, Ulrich Mueller wrote:
> > > > > > 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?
>
I suppose that would work for me. I'll wait a few more days, though, to
make sure we won't end up moving them twice over a short period.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
prev parent reply other threads:[~2024-01-08 13:44 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
2024-01-08 13:44 ` Michał Górny [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=c9df83725128d5470d60750be7a102edaf6b50cb.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.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