From: "Haelwenn (lanodan) Monnier" <contact@hacktivis.me>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New category: dev-build
Date: Sun, 7 Jan 2024 16:40:02 +0100 [thread overview]
Message-ID: <ZZrF0reJU9a0iEcw@cloudsdale.the-delta.net.eu.org> (raw)
In-Reply-To: <72604ee6acd03fb54bc6f664ce915ecd5b16566a.camel@gentoo.org>
[2024-01-07 15:46:23+0100] Michał Górny:
>Hi,
>
>Another idea for a new category: dev-build. Proposed description:
>
> Build systems and related tools.
>
>Some candidates (there are more):
>
[snip]
>sys-devel/gettext (not 100% sure about it)
I think that's the only one I wouldn't include as gettext seems to fit pretty
well in sys-devel/ as it's main purpose is to manipulate .po/pot files and
compile them in .mo files.
(gettext(3) et al being provided either by glibc/musl or by dev-libs/libintl)
prev parent reply other threads:[~2024-01-07 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 14:46 [gentoo-dev] [RFC] New category: dev-build Michał Górny
2024-01-07 14:50 ` Yuan Liao (Leo3418)
2024-01-07 16:20 ` Michał Górny
2024-01-08 1:18 ` orbea
2024-01-08 23:32 ` Gordon Pettey
2024-01-09 0:08 ` Eli Schwartz
2024-01-09 5:51 ` Michał Górny
2024-01-07 15:21 ` Arsen Arsenović
2024-01-07 15:40 ` Haelwenn (lanodan) Monnier [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=ZZrF0reJU9a0iEcw@cloudsdale.the-delta.net.eu.org \
--to=contact@hacktivis.me \
--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