From: David Seifert <soap@gentoo.org>
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 12:48:55 +0100 [thread overview]
Message-ID: <0c6db095b487c2a3894cfd97fcf0b37bcf99ca3a.camel@gentoo.org> (raw)
In-Reply-To: <8db6529b478c267afa679a9b91f27cd2@shitposting.expert>
On Fri, 2024-02-09 at 22:56 +0000, stefan11111 wrote:
> On 2024-02-09 21:56, Eli Schwartz wrote:
> > On 2/9/24 4:25 PM, Michael Orlitzky wrote:
> > > This is the part where you try to convince me that the things I
> > > want
> > > are stupid. OK. I don't care. I want it off. Leave me alone :)
> >
> >
> > As evidenced by the removal of libressl and eudev, this logic is
> > fallacious and wrong and not the way Gentoo is developed.
> >
>
> Both removals definitely not still being contested and debated.
>
> > Gentoo does indeed discuss the things that people want, and try to
> > determine whether they are useful to users, whether they are a
> > placebo,
> > and whether they are maintainable or have an adverse effect either
> > on
> > users or on the effort to maintain a consistent tree.
> >
> > So circling back around to the start of the thread:
> >
> > > pkgcheck complains about each new version of dev-lisp/sbcl:
> >
> > It is the allegation of the QA team that the option is a lie, it
> > contains no purpose or value and doesn't contribute to use choice,
> > and
> > pkgcheck is reporting the QA team's allegation.
> >
> > If you wish to convince the QA team otherwise, be my guest... but I
> > would personally encourage you to come up with a better argument
> > than
> > "the option makes me feel better about myself, I don't care what you
> > have to say, just leave my options alone goshdarnit; I have the
> > right
> > to
> > be stupid".
> >
> > Because I don't think you're likely to convince anyone like that.
> > Sorry.
>
> Maybe support as much choice as possible, and not act like you know
> what
> users want better that the users themselves.
>
Are users like you going to maintain and fix these obscure bugs too? I
don't recall seeing you sending in many fixes or patches, yet you seem
to be demanding that we go out of our way to accommodate you.
next prev parent reply other threads:[~2024-02-10 11:49 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
2024-02-10 11:48 ` David Seifert [this message]
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=0c6db095b487c2a3894cfd97fcf0b37bcf99ca3a.camel@gentoo.org \
--to=soap@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