4 ms·
If they are "optional", why do initrd generators need to know them? This truly has all the hallmarks of a systemd "solution"..
by stefan_ 3y ago
If they are "optional", why do initrd generators need to know them? This truly has all the hallmarks of a systemd "solution"..
- Denvercoder9 3y agoA dependency being optional on a technical level doesn't mean that it's optional on a functional level for everyone. `libfido2` mentioned in the pull request is a great example: if your rootdisk is encrypted using a FIDO token, you need that library in the initrd; but otherwise you don't. By making the dependency optional and initrd generators aware of that optional dependency, people that need it will have things just work, while others don't need to install the library.
- deleted 3y ago[deleted]
- kelnos 3y agoYou know that you use a token to unlock your boot device. You don't necessarily know the specific set of libraries needed to enable the feature, though.
- Spivak 3y agoBecause the optional dependencies actually do things. By default an initrd-builder would probably copy all deps including optional ones but it now enables you to choose not to do that as well, an avenue that was previously not available.