On Sat, 07 Mar 2020 13:32:17 +0800 Paul Wise <p...@debian.org> wrote: > On Fri, 2020-03-06 at 12:08 +0100, Patrick Matthäi wrote: > > > guichan isn't developed anymore. > > Ugh, I shouldn't have done a search, the situation is depressing. There > are projects for guichan on sourceforge, gitorious, google code and at > least three forks on github (one with another name). None of these > proclaim to be the official one or redirect to the others either :( > > Given the severity of the issue, lets leave it to a potential future > upstream maintainer of guichan, which may become me at some point as I > maintain mokomaze, one of guichan's reverse dependencies.
Upstream maintainer speaking here. :-) There's an official Guichan repository on GitHub now at https://github.com/darkbitsorg/guichan and today I've made a new Guichan 0.8.3 release, which includes most of the patches applied by Debian (excluding only the "Adds extended UTF8 support", so that one stays relevant until Guichan 0.9), a bunch of autoconf updates and added CMake support (still considered experimental). Among other things I think the new release addresses the issue of linking guichan_allegro to guichan, since I've added the following line: libguichan_allegro_la_LIBADD = $(top_builddir)/src/libguichan.la -lalleg In https://github.com/darkbitsorg/guichan/commit/51569b21a7d270d87ee002284556622e9beca88b. Guichan 0.8.3 should be binary compatible to 0.8.2 as long its still compiled using configure instead of CMake. Best regards, Thorbjørn Lindeijer
