portage-roles - A collection of portage roles for use with bosun(1)

	Commit message (Collapse)	Author	Age	Lines
*	boot-efi: Migrate boot USE-flag from init-systemd to boot-efi	Wolfgang Müller	2024-07-16	-1/+1
\| \| \| \| \|	The old gnuefi flag does not exist anymore, and a "generic" installation of systemd should not pull in the bootloader.
*	init-systemd: Bring in line with 23.0 hardened/systemd profiles	Wolfgang Müller	2024-03-23	-3/+0
\| \| \| \| \|	With the upstream addition of hardened/systemd profiles, we no longer have to set these settings manually.
*	init-systemd: Enable 'kernel-install' for systemd	Wolfgang Müller	2023-12-01	-1/+1
\|
*	init-systemd: Enable boot USE flag	Wolfgang Müller	2023-11-01	-1/+1
\| \| \| \| \|	We use systemd-boot and bootctl on at least one machine with the init-systemd profile, so enable it here.
*	init-systemd: Disable fido2	Wolfgang Müller	2023-05-02	-1/+1
\| \| \| \| \| \| \|	Because of [1] this will now pull in cryptsetup. Since there's no point in having fido2 enabled without it for now, we can simply disable it. [1] https://bugs.gentoo.org/902831
*	init-systemd: Enable tpm and fido2 USE flags for sys-apps/systemd	Wolfgang Müller	2022-11-08	-1/+1
\| \| \| \| \|	We have at least one machine with both a TPM chip and a FIDO2 device. It shouldn't hurt enabling this for every systemd-based system we have.
*	init-systemd: Remove 'cryptsetup' and 'fido2' USE flags	Wolfgang Müller	2022-04-28	-1/+1
\| \| \| \| \|	These are not needed in the general case and should instead be enabled in a host-specific profile.
*	Rename group-systemd to init-systemd	Wolfgang Müller	2022-04-28	-0/+4
	This more clearly describes what this profile does.