From: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] use.desc: Make `native-extensions` flag global
Date: Sun, 5 Nov 2023 01:08:31 -0500 [thread overview]
Message-ID: <ZUcxXwd0RNh_JaTG@dj3ntoo> (raw)
In-Reply-To: <20231105054235.312999-1-mgorny@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
On Sun, Nov 05, 2023 at 06:42:35 +0100, Michał Górny wrote:
> Make the `native-extensions` flag global. It is used in 15 Python
> packages to enable building optional C extensions, though the global
> description also allows for other "native" and "pure" languages.
>
> In 9 cases, the flag description explicitly mentions "speedups", so this
> is the primary case used in global description. There is one case
> of the extension providing extra features, and the remaining cases
> do not explain its role.
>
> Signed-off-by: Michał Górny <mgorny@gentoo.org>
> ---
> profiles/use.desc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/profiles/use.desc b/profiles/use.desc
> index d8f97958e900..01915ae78918 100644
> --- a/profiles/use.desc
> +++ b/profiles/use.desc
> @@ -212,6 +212,7 @@ musicbrainz - Lookup audio metadata using MusicBrainz community service (musicbr
> mysql - Add mySQL Database support
> mysqli - Add support for the improved mySQL libraries
> nas - Add support for network audio sound
> +native-extensions - Build native (C, Rust) extensions in additional to pure (e.g. Python) code (usually speedups)
I'd say "(e.g. C, Rust)", similarly to what you did later, so that
people don't think it means only C or Rust extensions get built.
- Oskari
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-05 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 5:42 [gentoo-dev] [PATCH] use.desc: Make `native-extensions` flag global Michał Górny
2023-11-05 6:08 ` Oskari Pirhonen [this message]
2023-11-05 12:00 ` Michał Górny
2023-11-05 13:44 ` Eli Schwartz
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=ZUcxXwd0RNh_JaTG@dj3ntoo \
--to=xxc3ncoredxx@gmail.com \
--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