* [gentoo-dev] Maintainer needed for >=app-admin/checksec-3.0.0:3 after upstream re-write in Golang
@ 2024-12-21 14:28 Sebastian Pipping
2024-12-22 0:46 ` Sam James
2024-12-22 2:08 ` Ionen Wolkens
0 siblings, 2 replies; 5+ messages in thread
From: Sebastian Pipping @ 2024-12-21 14:28 UTC (permalink / raw
To: gentoo-dev
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!
Best
Sebastian
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-dev] Maintainer needed for >=app-admin/checksec-3.0.0:3 after upstream re-write in Golang
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
1 sibling, 1 reply; 5+ messages in thread
From: Sam James @ 2024-12-22 0:46 UTC (permalink / raw
To: Sebastian Pipping; +Cc: gentoo-dev
Sebastian Pipping <sping@gentoo.org> writes:
> 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!
How do you propose the slot be handled? Do you plan to rename the 2.x
version as checksec-2 and have the :3 one be checksec or checksec-3?
>
> Best
>
>
>
> Sebastian
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-dev] Maintainer needed for >=app-admin/checksec-3.0.0:3 after upstream re-write in Golang
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 2:08 ` Ionen Wolkens
2024-12-22 15:53 ` Sebastian Pipping
1 sibling, 1 reply; 5+ messages in thread
From: Ionen Wolkens @ 2024-12-22 2:08 UTC (permalink / raw
To: gentoo-dev
[-- 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-dev] Maintainer needed for >=app-admin/checksec-3.0.0:3 after upstream re-write in Golang
2024-12-22 0:46 ` Sam James
@ 2024-12-22 15:38 ` Sebastian Pipping
0 siblings, 0 replies; 5+ messages in thread
From: Sebastian Pipping @ 2024-12-22 15:38 UTC (permalink / raw
To: Sam James; +Cc: gentoo-dev
On 22.12.24 01:46, Sam James wrote:
> How do you propose the slot be handled? Do you plan to rename the 2.x
> version as checksec-2 and have the :3 one be checksec or checksec-3?
I originally envisioned two slots: 0 and 3 (or 0->2 and 3 if someone
feels like a slot move). If it's considered beneficial to be two
separate packages blocking each other or using fully disjoint filenames:
no objections from my side. All I know is that the Bash version should
live on for a while more and that I'm not the right person for the
Golang ebuild, the rest is quite flexible. Thanks for your interest!
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-dev] Maintainer needed for >=app-admin/checksec-3.0.0:3 after upstream re-write in Golang
2024-12-22 2:08 ` Ionen Wolkens
@ 2024-12-22 15:53 ` Sebastian Pipping
0 siblings, 0 replies; 5+ messages in thread
From: Sebastian Pipping @ 2024-12-22 15:53 UTC (permalink / raw
To: gentoo-dev
On 22.12.24 03:08, Ionen Wolkens wrote:
> I'm confused, why is slotting needed? Is there a reason to ever install
> both versions at same time?
With 3.0.0 being so new and not providing feature parity with 2.7.1 yet
I felt that some period of co-existence could help the transition period.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-12-22 15:53 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2024-12-22 15:53 ` Sebastian Pipping
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox