From: Hank Leininger <hlein@korelogic.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] More packages up for grabs due to developer inactivity
Date: Wed, 14 Feb 2024 12:38:06 -0700 [thread overview]
Message-ID: <20240214121804.7fd1c35a-f861-4184-9f7a-651955b7bfc2@korelogic.com> (raw)
In-Reply-To: <fec51b91a6107e9fbd589a610312e5382afc78aa.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On 2024-02-14, mgorny said:
> The following packages are also left with no maintainer:
...
> app-misc/binwalk
I use this, I can p-m it.
However, upstream seems partly, if not mostly dead (last PR merged was a
year ago, only 3 merged in the last ~2.5 years, 50+ outstanding PRs,
100+ outstanding issues). There's some more active forks, but none that
has yet unambiguously taken over the project. I'd welcome guidance on
when to decide to switch forks in SRC_URI vs carrying around
cherry-picked patches in files/.
If there's a GLEP covering this scenario I couldn't find it; offlist
would be fine unless my inability to Google is a useful learning moment
for others.
Thanks,
--
Hank Leininger <hlein@korelogic.com>
8428 ED14 5268 C727 0C48 F454 846F 0637 5FEB 1612
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-14 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 10:38 [gentoo-dev] More packages up for grabs due to developer inactivity Michał Górny
2024-02-14 11:30 ` Gerion Entrup
2024-02-14 14:47 ` orbea
2024-02-14 15:25 ` stefan11111
2024-02-14 15:29 ` Ionen Wolkens
2024-02-14 15:59 ` Michał Górny
2024-02-14 19:38 ` Hank Leininger [this message]
2024-02-14 20:23 ` Conrad Kostecki
2024-02-14 23:12 ` Ionen Wolkens
2024-02-15 13:07 ` [gentoo-dev] Re: [gentoo-dev-announce] " Bernard Cafarelli
2024-02-16 12:57 ` Marc Schiffbauer
2024-02-17 9:44 ` [gentoo-dev] " Zoltan Puskas
2024-02-14 22:52 Hank Leininger
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=20240214121804.7fd1c35a-f861-4184-9f7a-651955b7bfc2@korelogic.com \
--to=hlein@korelogic.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