From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New category: dev-build
Date: Tue, 09 Jan 2024 06:51:03 +0100 [thread overview]
Message-ID: <6798345aa52d4b4cc2ebae2450bd3226fe9fcb60.camel@gentoo.org> (raw)
In-Reply-To: <CAHY5MedGUUj1eWqJMRt78_LU0_49De7zU6bX-YxGWW7YEPKi9g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
On Mon, 2024-01-08 at 17:32 -0600, Gordon Pettey wrote:
> There are at least a few generally language-specific build
> tools/systems that can, if you're into masochism, be used to build
> other languages (Gradle, Maven, etc.), and tools like Ant, which while
> primarily used in Java projects is really just a Makefile with
> different syntax and core functions in XML. Does making a new category
> for explicitly general-purpose tools like Make and friends ambiguate
> where the language-specific tools belong? Should other
> non-Make-related packages be moved from their current dev-[language]
> locations?
>
> Does dev-util/gyp really belong there, or since it is node-specific,
> should there be a dev-js category?
>
In all of my RFCs, I've tried to keep moving stuff out of dev-
<language>/* altogether. In general, I'd leave it to the maintainers to
decide where a package fits best.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2024-01-09 5:51 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 [this message]
2024-01-07 15:21 ` Arsen Arsenović
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=6798345aa52d4b4cc2ebae2450bd3226fe9fcb60.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