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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Sebastian Pipping <[email protected]> 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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEx3SLh1HBoPy/yLVYskQGsLCsQzQFAmdndJoACgkQskQGsLCs QzQ6ewgAxbe/PSRUoFYErNOuBhrynKgtxmdqj5O10tleDaZh2UiUBHtuBApFCa1h n7mUBPFzIvt2LcYI1cTFjyatmpVNTnDeWT0UxivFwBWkzMQe6R+8T7ge+74ywPuG Y/ySX/1qH0YzeUT4mp4T6mP/yEKLHYeeJ9Pem8xHtXbmZRTqwj18EflnRkXuJPee WJJKkNckBiZoO+tBqnwRJI3bNV87Ca4pln8dHIMWXwqHKdUrO3UGSvtTgUDWNFVJ C0QK5USEJ8u7OgWPWWfEnJEu37KTK7lFFk+wQ3Roxc/vWulODy1kv+n56LWrda+T KPr/R3m5a7JntjmauuLA8HOfjskjXQ==
=mu57
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)