Re: (gnu)chess, I'm building it

[Goswin Brederlow <goswin.brederlow@student.uni-tuebingen.de>]

James Troup <james@nocrew.org> writes:

> Philip Blundell <pb@nexus.co.uk> writes:
> 
> > >A week might be conservative.  I've been building the package for
> > >2 or 3 days now and haven't made much of a dent.  I'll kill the
> > >build; there's quite a bit to do now.
> > 
> > Yeah, it takes several days on ARM too.
> 
> It takes 9 hours on a fast[1] i386, easily dwarfing most other
> packages[2].  Unfortunately the maintainer isn't overly responsive to
> this (see #102272 etc.) and Debian issues in general (see BTS, his
> packages etc.).
> 
> IMNSHO this package should be ignored[3] until the maintainer can be
> convinced to do something other than a grand imitation of an ostrich.
> If you build it once, you're merely committing your architecture to
> keeping it up to date.

I've split gnuchess into gnuchess and gnuchess-book, the later
containing the bookfile that is so painstakenly generated, but in a
arch indep format. Upon install it gets converted to the hosts
architecture (just takes a few seconds).

I submitted a bugreport with patch for gnuchess in case anyone wants
to look at it. It fixes all (?) of the reported bugs on gnuchess and
the arch-indep build only takes a few minutes.

Should I do a NMU unless the maintainer reacts in the next few hours?
Do I (you?) have to do anything to enable autocompile on the buildds
for it?

MfG
        Goswin