[Pkg-crosswire-devel] peaceful coexistence of libsword6 and libsword7

Jonathan Marsden jmarsden at fastmail.fm
Wed Jan 28 17:19:08 GMT 2009


Raphaƫl Pinson wrote:

> Just tried packages from your PPA. It seems libsword7 should conflict with
> libsword6, since they both provide /usr/bin/imp2gbs .

Yes, thanks for the reminder!  In their current state, they should.

We've talked on the list a litle about putting the tools into a separate
package say libsword-tools, or all into the diatheke package even -- but
there's not consensus in the group on doing that at this point.  Your
input would be appreciated, if you have an opinion and the time to join
the discussion!

My current (maybe naive?) thinking is that it would be helpful if, down
the road, one could install libswordN and libswordN+1 (indeed, for
libraries, I think this is much of why one embeds a SONAME version in
the package name itself!).  But the older libswordN (for N <=6)
packaging did not allow for this.

The libsword7 packages are definitely not ready for release yet; they do
seem to work fine for me and for Dima on machines without libsword6, at
least.  And my biblememorizer package sees them and uses them fine,
which is good (previously I'd only tested with diatheke).

How hard (and how worthwhile) is it likely to be to get things to the
point where the different versions of libswordN will coexist?  Am I just
making trouble for myself by attempting that?  Several other library
packages do seem to manage it... so I'm not totally nuts to be thinking
this way... am I?

Jonathan




More information about the Pkg-crosswire-devel mailing list