Hi, On Fri, 2012-05-11 at 19:09 +0200, Evgeni Golov wrote: > 2. taxbird should also depend on the proper libgeier binary. I am not > sure whether it is a good idea to leave the soname of the binary at 0 > all the time. IMHO it should be bumped on every incompatible release.
I think the soname shouldn't be bumped, since the library's code doesn't actually change at all. libgeier is shipped with a bunch of XSD & XSL files, which are needed to validate the data against the rules as specified by Germany's fiscal authorities. As those rules change from year to year, further XSDs are added every year. The C-library just picks the XSD by certain rules and uses it, i.e. there's no change required in the library itself. Or, to put it another way, if you'd split libgeier into three packages (libgeier0, libgeier-dev, libgeier-data - the latter with the XSD & XSL files), newer taxbird version could live with older libgeier0, but require an up-to-date version of libgeier-data (since it relies on libgeier to be able to validate the data and apply stylesheets) > On a related topic: is libgeier incompatible in both directions? > Your explanation says taxbird+1 needs libgeier+1. But would an older > taxbird work with the newer libgeier? If not, soname bump is the way > to go. Older taxbird versions happily work with newer libgeier versions. cheers, stesie -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
