A Dilluns 29 Setembre 2008, Neil Williams va escriure: > On Mon, 29 Sep 2008 17:31:55 +0200 > > Leopold Palomo Avellaneda <leo@alaxarxa.net> wrote: > > Hi, > > > > I'm packing a library (not yet an ITP, just learning) and I'm having some > > doubts about it. > > > > Upstream uses autotools, but not in a very correct way, I guess. The > > library is 3.5.6 version, but the configure + make creates > > libXXX.so.0.0.0. I have looked on the configure.ac, Makefile.am, etc, and > > I have not seen any place to pass a parameter to libtoolize. So, how can > > I "correct" this bug in upstream? > > IT IS NOT A BUG! > > The version of a library has nothing to do with the SONAME. Please read > the libtool manual. Yes, you are right. But I prefer the Debian library packaging guide, it's more clear in this aspect. However I guess than the author uses the version number as the SONAME number and don't know how to change it. Because I think that the different versions of the library have broken the binary compatibility. But, if I should leave the version numbers as the authors want, no problem. > > Also, my second question is about to create a dbg package. Upstream has > > some --enable-debug that is a -DDEBUG. Looking on the source I have seen > > some std outs with this define. Looking others packages, I have > > understood that you create the package normally, and you add > > > > dh_strip --dbg-package= > > > > line to put the striped symbols in that package. This is correct? is it > > worsewhile to generate that package? > > It is worthwhile to create the -dbg but let the build tools create it > for you. Ok. > > And my last question is examples. Upstream has a directory with some > > examples, but they are not installed (noinst_PROGRAMS), so, should I to > > patch sources to install them? Or simply, do I copy the files? > > noinst_PROGRAMS should not be packaged, generally. Some can be upstream > test cases. In this case are examples. thanks for the answer. best regards, Leo -- -- Linux User 152692 PGP: 0xF944807E Catalonia
Attachment:
signature.asc
Description: This is a digitally signed message part.