From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Maintainer needed for >=app-admin/checksec-3.0.0:3 after upstream re-write in Golang
Date: Sat, 21 Dec 2024 21:08:27 -0500 [thread overview]
Message-ID: <Z2d0m7di74pdlbwT@eversor> (raw)
In-Reply-To: <b1cc19a5-5707-4a5a-97d0-d3737ea2e1d7@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
On Sat, Dec 21, 2024 at 03:28:55PM +0100, Sebastian Pipping wrote:
> Hi!
>
>
> This is basically https://bugs.gentoo.org/946784 and a call for help via
> e-mail to a wider audience:
>
> I've been maintaining the Bash version of app-admin/checksec 2.x.x so
> far but I won't be a good maintainer of a >=3.0.0 ebuild targeting
> Golang that upstream switched to. If you can help with a proper :3
> slotted Golang ebuild for checksec >=3.0.0 (while not deleting Bash-
> based app-admin/checksec:0, I can keep maintaining 2.x.x) that would
> rock. Please just assign the ticket to you in that case to avoid
> unintended duplication. Many thanks in advance!
I'm confused, why is slotting needed? Is there a reason to ever install
both versions at same time?
The old version can keep existing either way assuming it's not broken
and someone wants it.
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-12-22 2:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 14:28 [gentoo-dev] Maintainer needed for >=app-admin/checksec-3.0.0:3 after upstream re-write in Golang Sebastian Pipping
2024-12-22 0:46 ` Sam James
2024-12-22 15:38 ` Sebastian Pipping
2024-12-22 2:08 ` Ionen Wolkens [this message]
2024-12-22 15:53 ` Sebastian Pipping
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=Z2d0m7di74pdlbwT@eversor \
--to=ionen@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