public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] special small-files USE flag without effect on dependencies: [ unicode ]
Date: Fri, 09 Feb 2024 12:17:49 -0500	[thread overview]
Message-ID: <6eae895976c68d4c4a4d2036476d4d100c63c797.camel@gentoo.org> (raw)
In-Reply-To: <CAJ0EP425yxSP4tXhmU7fhzXjAhdSWQ=ybX_0ejPAojYpqn+g4w@mail.gmail.com>

On Fri, 2024-02-09 at 11:57 -0500, Mike Gilbert wrote:
> 
> Based on this pkgcheck issue, this originates from a decision from by
> Gentoo QA team.
> 
> https://github.com/pkgcore/pkgcheck/issues/414#issuecomment-1213057268
> 

Thanks for the dig. I agree with the reasoning for things like
USE=bash-completion and USE=vim-syntax, where the added complexity of a
flag is not justified to avoid installing small files. In those cases,
the additional files simply don't do anything if you don't (for
example) use vim.

USE=unicode and USE=ipv6 are different beasts. In many cases they
directly and immediately change the behavior of the package. I think
that there are good reasons to want those two disabled, but the user's
reasoning shouldn't really matter. The only "problem" in this case is
the pkgcheck warning. Upstream supports it, the maintainer supports it,
it works, users might want it, and it's one of our selling points.
Given all of that, I'm leery of treating it like some kind of mistake.



  reply	other threads:[~2024-02-09 17:17 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 [this message]
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
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=6eae895976c68d4c4a4d2036476d4d100c63c797.camel@gentoo.org \
    --to=mjo@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