>>>>> On Mon, 21 Aug 2023, Redjard wrote: > I did consider doing so, however with that approach my effective fork > of the kernel.eselect module would get continually outdated, while a > wrapper module requires a different command [...]
Not necessarily. It could use the same name as the original module,
after adjusting the modules path:
ESELECT_MODULES_PATH=( "${ESELECT_DEFAULT_MODULES_PATH}" )
Still, I'd not recommend using the same name when its behaviour is
different from the original module.
