Ok, fair point about the XKB stuff. I didn't realize this type of problem was so common. No pressure to add in all those trivial packages if so.
A better solution might be to just show me what real errors look like during the make process. Just to be clear, the only reason I was even looking for errors is because of the message "If there are no errors, you're ready to build." Instead of listing every trivial package, maybe you could just explain that message by showing the exact wording of what an error looks like. Any trivial package like the XKB ones wouldn't matter then, because the message associated with missing packages would presumably not match the wording of a true error.
Also, you were right. I was mistakenly running version 19 of the test plugin because the build page for Linux (
https://github.com/Sigil-Ebook/Sigil...ng_on_Linux.md) still linked directly to it. Maybe instead of a direct link you could just tell people to look for it under the docs folder in the repo. That would spare you the trouble of remembering to update the link every time there's a new version of the test plugin.