Re: reduce/simplify the maintenance of sec-keys packages

Hank Leininger <[email protected]> Tue, 16 Jun 2026 13:10:47 -0600

Newsgroups	gmane.linux.gentoo.devel
Message-ID	<20260616125946.7e0b6f8d-40bb-43b0-aa3b-b6dc6b645bfb@korelogic.com>

On 2026-06-16, Agostino Sarubbo wrote:
> I have not analyzed whether this is technically possible, but I am
> wondering whether it would make sense to create a dedicated Git
> repository on GitWeb, store all keys there, and have a single ebuild
> that installs all of them.

I p-m a few packages, have added sec-keys for some and would like to do
so for more over time.

Adding a key and adding/updating a package ebuild to add verify-sig
support referencing that key is doable in multiple commits in a single
PR, so it's atomic from the perspective of ::gentoo users.

Sometimes a project changes key and we need old-key in-tree for PV 1.2.3
and new-key for PV 1.2.4.

Both of those sound like they might be made harder, not easier, by your
proposal?

Thanks,

-- 

Hank Leininger <[email protected]>
8428 ED14 5268 C727 0C48  F454 846F 0637 5FEB 1612

signature.asc (application/pgp-signature, 870 B)