[Pkg-crosswire-devel] Thoughts on sword-frontend and packaging sword modules

Dmitrijs Ledkovs dmitrij.ledkov at gmail.com
Mon Aug 17 18:54:48 BST 2009


* Is there a need for virtual package "sword-frontend"?

Sword library package suggest to install sword-frontend. Previously
sword-frontend was provided by bibledit, xiphos and I think
biblememorizer. But if someone installs libsword8 directly (e.g. via
synaptic / kpackagekit), apt will try to satisfy sword-frontend
dependency in alpha-numerical order and hense bibledit gets pulled in.

Can I go ahead and kill virtual sword-frontend cause I don't quite see
use for it?

Similar virtual package "sword-text" was previously causing for the
arabic bible to be pulled in cause arabic bible is "sword-text-arasvd"
and it is sorted first alphanumerically.

* About packaging crosswire texts

I've played around with Jonathan's scripts. Scripts are nice =) But
this scripts are packaging binary files from a raw zip file into a

Something that would be great is to actually get hold of source (eg
OSIS formatted texts) and then use $format2mod utilities to build
these modules and recreate from scratch files that are packaged in

First of all this will stress-test $format2mod utils for generating
modules and will be able to notice regressions in the sword utils.

This brings another hot topic =)

If we actually want to build modules from sources then we need
sword-utils package =) cause otherwise we'll have to build depend on
each libsword soname package (libsword8, libsword9 etc)

Thoughts ? Comments? =)

With best regards

Dmitrijs Ledkovs (for short Dima),
Ледков Дмитрий Юрьевич

More information about the Pkg-crosswire-devel mailing list