[ ] Using the ini plugin doesn't work, because of the multiline description metakeys. (I switched to ni for now, but its file format is not ideal).
[ ] Parts of the specifications are still commented out because of the max plugins issue.
[ ] Not all drivers are updated. The specification is based on the old example LCDd.conf; not all config keys for drivers are included. The updated drivers have a full specification.
[ ] Once all drivers are updated, the rather big specification for LCDd will probably slow down the server start-up time as well as any (cascading) kdb operation that calls the spec plugin on the relevant mountpoint. Dynamically enabling/disabling parts of the specification would be nice, although I don't see any way to do this right now.
[ ] Improving the spec plugin performance would also be nice, but again, I don't know how.
[ ] Various known issues with the kdb tool that make using it hard. Especially the fact that kdb set -N user <cascading-key>, may result in a broken configuration (because of the origvalue metadata).
@kodebach wrote in #2815:
iniplugin doesn't work, because of the multilinedescriptionmetakeys. (I switched tonifor now, but its file format is not ideal).LCDd.conf; not all config keys for drivers are included. The updated drivers have a full specification.LCDdwill probably slow down the server start-up time as well as any (cascading)kdboperation that calls thespecplugin on the relevant mountpoint. Dynamically enabling/disabling parts of the specification would be nice, although I don't see any way to do this right now.specplugin performance would also be nice, but again, I don't know how.kdbtool that make using it hard. Especially the fact thatkdb set -N user <cascading-key>, may result in a broken configuration (because of theorigvaluemetadata).