* Oohara Yuuma <ooh...@libra.interq.or.jp> [130404 09:26]: > The upstream makefile says: > > > libtcod.so : $(TEMP)/libtcod/release $(LIBOBJS_C_RELEASE) > > gcc -shared -Wl,-soname,$@ -o $@ $(LIBOBJS_C_RELEASE) $(ZLIB_LIBS) > > $(PNG_LIBS) $(SDL_LIBS) $(CFLAGS) $(OPENGL_LIB) > > Please discuss the SONAME version with the upstream before packaging.
Sure. I just used "0" in my preliminary packaging work but the lack of soname may be a problem. I'm afraid that it won't be easy to convince upstream as the library has an history of API breakage [1]. Do you know if we have a comprehensive "how-to" / "why" document to explain these problems ? The upstream guide [2] mentions a library guide [3], and there's also [4] but everything is good to be forwarded. If upstream is not interested, I believe that the best solution is to package a static library (or embed it into the brogue source package) but I'd like to avoid that. Thanks [1]: http://upstream-tracker.org/versions/libtcod.html [2]: http://wiki.debian.org/UpstreamGuide [3]: http://davidz25.blogspot.fr/2011/07/writing-c-library-part-5.html#abi-api-versioning [4]: http://semver.org/ -- Etienne Millon -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130404074433.GA4689@klow
