Hi Hamish, [snip] >Cool. I started on packaging, but I've encountered a problem. libgeda is >still version 31 so existing gschem binaries will use it. However when >gschem 1.2.0 is run with the libgeda from 1.2.1, it just quietly exits. >strace shows that it is actually segfaulting and catching it.
Why are you running gschem 1.2.0 with libgeda 1.2.1? That is not supported. Please don't tell me that Debian allows that sort of thing. All of 1.2.0 should use 1.2.0 versions. All of 1.2.1 should use 1.2.1 versions. In 1.2.1, libgeda should be 31:1:0. In 1.3.0, libgeda should be 32:0.0. I know I just violated a .so numbering convention here (but I didn't expect the changes in 1.2.1 to be so incompatible with 1.2.0), but I've never heard of anybody getting bitten by these indiscretion. I've probably also said in the past that I always bump the major number of the so, but I didn't in this release. I suppose I could change libgeda's so number to 33:0:0, but that would be odd since 1.3.0 is using 32:0.0. Does the way libgeda is released and numbered cause that many problems for you and Debian? If so, what can I do to make your life easier in this regard? Thanks, -Ales _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
