Why is this considered a 'bug', and why does this need fixing at all?
Opening books are (often very) bulky architecture-independent data, which does not belong in binary packages. That holds both for XBoard and for GNU Chess. Books should go in their own package.
In addition, XBoard is not dependent on any engine for handling opening books; it can handle such books directly. The user just has to give the filename of the book (through a file-browse dialog, if desired) and tick a checkbox to enable its use. Having engines handle the book is a stupid way to do it, because then you still wouldn't have a book when you want to use another engine.
Why is this considered a 'bug', and why does this need fixing at all?
Opening books are (often very) bulky architecture- independent data, which does not belong in binary packages. That holds both for XBoard and for GNU Chess. Books should go in their own package.
In addition, XBoard is not dependent on any engine for handling opening books; it can handle such books directly. The user just has to give the filename of the book (through a file-browse dialog, if desired) and tick a checkbox to enable its use. Having engines handle the book is a stupid way to do it, because then you still wouldn't have a book when you want to use another engine.
H.G. Muller
upstream XBoard developer