public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Maintainer needed: dev-db/sqlite
Date: Fri, 14 Jan 2022 23:59:15 +0000	[thread overview]
Message-ID: <08FAC0B8-5231-4B3A-A54A-67BC99C31132@gentoo.org> (raw)
In-Reply-To: <20220114231003.15610.qmail@stuge.se>


[-- Attachment #1.1: Type: text/plain, Size: 2501 bytes --]



> On 14 Jan 2022, at 23:10, Peter Stuge <peter@stuge.se> wrote:
> 
> Mike Gilbert wrote:
>> The current (proxied) maintainer is somewhat difficult to work with
> 
> Why is Arfrever being treated so bad here? To me, it looks like
> you're the one who is difficult to work with. :\
> 

floppym is not obligated to work with somebody if he finds it
difficult.

> 
> Jakov Smolić wrote:
>> From what I've investigated, other major distributions don't apply
>> any similar patches which means that we are likely to stop carrying
>> most (or even all) of the current patches.
> 
> What kind of silly groupthink is this? I expect Gentoo to champion choice.

Adding in a huge heap of patches which exceed the tree limits, have
no justification within them, and nobody else needs is a good reason
to dump them.

If someone actually wants them, that's another matter.

Even if they are being kept, justification for them should be made
so that others know why we're doing it, why it's worth rebasing them,
why we're changing the default behaviour of SQLite, ...

(This is all worth doing anyway, but Gentoo, if we're going to do
tropes, also doesn't like to deviate from upstream without
justification.)

Please don't bring out this cliched "choice" trope just because
we're discussing something. Obviously if they're actually useful
in an application, we can talk about keeping them.

> 
> 
> Mike Gilbert wrote:
>> There is an open QA bug [1] regarding the large set of undocumented
>> patches that are being applied in the stable ebuilds.
> 
> Arfrever is active in the bug you linked, has provided explanations
> for the patches and prepared to restructure the patches so that they
> can be gated by local USE flags, has made several different concrete
> suggestions for possible implementations and requested feedback, but
> has received no reply in the bug and instead there's now this
> backstabbing discussion on this list.
> 

You've missed discussions on IRC and some of the bugs _have_
gone unanswered (in particular https://bugs.gentoo.org/825278 <https://bugs.gentoo.org/825278>
which started this all off).

Also, we were waiting several months for new SQLite which
blocked security bumps for e.g. seamonkey.

He has also received replies on the bug.

> Really?
> 

You've intervened in something where you don't know all the
circumstances, including the history of the contributor,
with an aggressive tone. Really?

sam


[-- Attachment #1.2: Type: text/html, Size: 4103 bytes --]

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2022-01-14 23:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 17:53 [gentoo-dev] Maintainer needed: dev-db/sqlite Mike Gilbert
2022-01-14 18:07 ` Jakov Smolić
2022-01-15  1:14   ` Mike Gilbert
2022-01-14 23:10 ` Peter Stuge
2022-01-14 23:59   ` Sam James [this message]
2022-01-15  0:52   ` Mike Gilbert

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=08FAC0B8-5231-4B3A-A54A-67BC99C31132@gentoo.org \
    --to=sam@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