Hi Stefan,

On Sat, May 12, 2012 at 08:42:35PM +0200, Stefan Siegl wrote:

> 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.

Thanks a lot for the clarification!

Did I get it right, I actually can mix geier and taxbird as I like (if I 
patch taxbird a bit), but will be able to do my taxes up to the year 
geier's data supports it?

Then I think the long-term perfect solution would be some sort of 
metadata in libgeier(-data) which taxbird can read and inform the user 
about. Then a build-time check isn't needed.

I wonder how http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529376 
fits in this picture. Tax data for a too new year I guess?

For the time being, I think the before-mentioned patches should "fix" 
the issue, right? They would properly tight the depends (build and 
runtime).

Regards

-- 
Bruce Schneier can read and understand Perl programs.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to