Package: gpsshogi Version: 0.3.0-1 Severity: normal Here are a couple of differences with gnushogi on which I stumbled, while trying to use gpsshogi with omaha (http://repo.or.cz/w/omaha.git). Note that in supporting gnushogi I have not tried to mimic xshogi (which at least does stange things to disable time control), but attempted to do something sane that works :)
I'm also aware that CSA is the primary protocol for gpsshogi, but since I have xshogi support already implemented, I wanted to see if gpsshogi could be supported easily. * to exit gpsshogi, "quit" or "exit" do not work but EOF does, whereas it is the reverse for gnushogi. Is killing (eg. ^C/SIGINT the only shared way ?) * move output by gpsshogi have 2 spaces between move and time, whereas gnushogi only has one. My parser was easily made more tolerant, but maybe other frontends are more strict... * when issued command "black", gpsshogi starts playing right away, whereas gnushogi requires to be given command "go" first. Looks like implicit color switch is more portable, but it seems a bad idea to implement this command at all it it behaves differently. * in response to a valid move, gnushogi answers with a confirmation line, whereas gpsshogi only displays something in case of error. All in all that looks like the only behaviour that a "trivial fix" of a fronted relying on it can't handle. y...@home:/work/yann/games/omaha$ gpsshogi gpsshogi (compatible with GNU Shogi) go 1. ... 7g7f 149900 3c3d 2. ... 2g2f 149800 ^C y...@home:/work/yann/games/omaha$ gnushogi GNU Shogi 1.3.2p0 go 1. ... 7g7f 299530 3c3d 1. 3c3d 295600 2. ... 6g6f 298210 ^C A couple of less important ones too: * Having the version number of gpsshogi written on 1st line would help identify what program is playing * having a short list of supported commands in response to "help" would help to understand what subset of commands is supported by gpsshogi * another commands appear to be easy to support, having commandline flag equivalents is "easy" / --opponent-time -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34.1-00003-ge5b0813-dirty (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gpsshogi depends on: ii gpsshogi-data 0.3.0-1 data files for gpsshogi ii libboost-filesystem1.42.0 1.42.0-3 filesystem operations (portable pa ii libboost-program-options1 1.42.0-3 program options library for C++ ii libboost-system1.42.0 1.42.0-3 Operating system (e.g. diagnostics ii libboost-thread1.42.0 1.42.0-3 portable C++ multi-threading ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-6 GCC support library ii libgsl0ldbl 1.14+dfsg-1 GNU Scientific Library (GSL) -- li ii libncurses5 5.7+20100313-2 shared libraries for terminal hand ii libosl1 0.3.0-1 library for Shogi playing programs ii libpocofoundation9 1.3.6p1-1+b1 The C++ Portable Components Founda ii libpoconet9 1.3.6p1-1+b1 The C++ Portable Components Networ ii libqt4-network 4:4.6.3-1 Qt 4 network module ii libqt4-qt3support 4:4.6.3-1 Qt 3 compatibility library for Qt ii libqt4-xml 4:4.6.3-1 Qt 4 XML module ii libqtcore4 4:4.6.3-1 Qt 4 core module ii libqtgui4 4:4.6.3-1 Qt 4 GUI module ii libreadline5 5.2-7 GNU readline and history libraries ii libstdc++6 4.4.4-6 The GNU Standard C++ Library v3 ii libtcmalloc-minimal0 1.5-1 an efficient thread-caching malloc gpsshogi recommends no packages. gpsshogi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
