public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New category: dev-build
Date: Sun, 07 Jan 2024 16:21:32 +0100	[thread overview]
Message-ID: <87zfxhgo98.fsf@gentoo.org> (raw)
In-Reply-To: <72604ee6acd03fb54bc6f664ce915ecd5b16566a.camel@gentoo.org>

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

Hi!

Michał Górny <mgorny@gentoo.org> writes:

> Hi,
>
> Another idea for a new category: dev-build.  Proposed description:
>
>   Build systems and related tools.
>
> Some candidates (there are more):
>
> dev-util/bazel
> dev-util/cmake
> dev-util/cmake-fedora
> dev-util/gn
> dev-util/gtk-doc-am
> dev-util/gyp
> dev-util/meson
> dev-util/muon
> dev-util/netsurf-buildsystem
> dev-util/ninja
> dev-util/samurai
> dev-util/tup
> sys-devel/autoconf*
> sys-devel/automake*
> sys-devel/bmake
> sys-devel/cons
> sys-devel/gettext (not 100% sure about it)

That's a bit of a toss-up, but I think I lean more towards the side of
sys-libs or so (since, while it indeed provides build-time tools, it is
not really a build system component, and it provides a few other libs).

> sys-devel/libtool
> sys-devel/make
> sys-devel/pmake
> sys-devel/qconf
> sys-devel/slibtool

I like the idea.

Have a lovely day!
--
Arsen Arsenović

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

  parent reply	other threads:[~2024-01-07 15:24 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ć [this message]
2024-01-07 15:40 ` Haelwenn (lanodan) Monnier

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=87zfxhgo98.fsf@gentoo.org \
    --to=arsen@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