public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] use.desc: Make `native-extensions` flag global
Date: Sun, 5 Nov 2023 08:44:47 -0500	[thread overview]
Message-ID: <851939c3-6cdd-4fce-a040-f247d0c0132a@gmail.com> (raw)
In-Reply-To: <20231105054235.312999-1-mgorny@gentoo.org>

On 11/5/23 1:42 AM, 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.


The USE flag's name inherently feels like something aligned with
building speedups, so why not dedicate it to that purpose? It feels
confusing to have a global USE that does different things for different
packages.

It sounds like just renaming a single USE flag -- peewee from
"native-extensions" to "sqlite-ext" -- would be enough to allow nicer
semantics here.


-- 
Eli Schwartz



      parent reply	other threads:[~2023-11-05 13:44 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
2023-11-05 12:00   ` Michał Górny
2023-11-05 13:44 ` Eli Schwartz [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=851939c3-6cdd-4fce-a040-f247d0c0132a@gmail.com \
    --to=eschwartz93@gmail.com \
    --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