public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Jolly <Matt.Jolly@footclan.ninja>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] special small-files USE flag without effect on dependencies: [ unicode ]
Date: Sat, 10 Feb 2024 10:03:33 +1000	[thread overview]
Message-ID: <85f5ba6f-54f8-4fc1-915a-622fd868cd92@footclan.ninja> (raw)
In-Reply-To: <8db6529b478c267afa679a9b91f27cd2@shitposting.expert>

On 10/2/24 08:56, stefan11111 wrote:
 > Both removals definitely not still being contested and debated.

You've conveniently ignored the context immediately below the line that
you chose to quote and somehow decided to try and shoehorn in discussion
of a completely different (and settled) issue. Congratulations, it's not
often that I get to open my emails in the morning and untangle several
different flavours of wrong in only a single line!

 > Maybe support as much choice as possible, and not act like you know what
 > users want better that the users themselves.

FYI I don't appreciate your tone. Purge it down a little next time,
please?

Knowing what's best for users, especially when the users in question
appear to be willfully misinformed, is actually part of a developer's
job description. We even have a fancy section of the dev manual that's
all about not adding superfluous USE flags because we've learnt through
experience that providing a toggle for every single little thing in a
package is not, in fact, beneficial to users overall.

https://devmanual.gentoo.org/general-concepts/use-flags/index.html#when-not-to-use-use-flags

Users _rely_ on developers to make sane decisions on their behalf,
particularly around which USE options should exist and be togglable and
which options it makes sense to just hard enable or disable in the
configure step. In general we don't expect users to have an in-depth
knowledge of an upstream build system; they don't need to be across the
implementation details of every single configure option, they just need
to trust the options enabled by ebuild developers (and by extension the
decisions made by the wider project, including [and especially] areas
like QA).

In addition to this there are mechanisms through which a user can choose
to override the decisions made within an ebuild, including but not
limited to the already-mentioned EXTRA_ECONF, MYMESONARGS, MYCMAKEARGS
in package.env.

TL;DR: Methinks thou dost make too great a mountain of that which is but
a molehill

On to the main subject, we already default USE=unicode to on in the
ebuild and a browse over the sbcl docs suggests that it's also the
upstream default and is unlikely to break anything given that it's been
that way since version 0.8.17 and we're well into major version 2 by
now. Just drop the USE and default it to on - QA is right in this case:
in the absence of a compelling reason to keep the USE it should be
dropped.

Cheers,

Matt


  reply	other threads:[~2024-02-10  0:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 15:23 [gentoo-dev] special small-files USE flag without effect on dependencies: [ unicode ] Andrey Grozin
2024-02-09 15:43 ` Mike Gilbert
2024-02-09 15:54 ` Ionen Wolkens
2024-02-09 16:07   ` Michael Orlitzky
2024-02-09 16:57     ` Mike Gilbert
2024-02-09 17:17       ` Michael Orlitzky
2024-02-09 18:40         ` Mike Gilbert
2024-02-09 19:09         ` Eli Schwartz
2024-02-09 19:57           ` Michael Orlitzky
2024-02-09 21:04             ` Eli Schwartz
2024-02-09 21:25               ` Michael Orlitzky
2024-02-09 21:56                 ` Eli Schwartz
2024-02-09 22:56                   ` stefan11111
2024-02-10  0:03                     ` Matt Jolly [this message]
2024-02-10 11:48                     ` David Seifert
2024-02-10 17:26                       ` stefan11111
2024-02-11  0:58                         ` Eli Schwartz
2024-02-10 11:22                   ` orbea
2024-02-11  0:58                     ` Eli Schwartz
2024-02-10  0:04               ` Sam James
2024-02-11  0:42                 ` Eli Schwartz
2024-02-11  3:46                   ` Sam James
2024-02-11  3:56                     ` Eli Schwartz
2024-02-12  4:54                     ` Andrey Grozin
2024-02-10  0:00             ` Sam James
2024-02-09 23:52 ` Sam James

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=85f5ba6f-54f8-4fc1-915a-622fd868cd92@footclan.ninja \
    --to=matt.jolly@footclan.ninja \
    --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