[Pkg-crosswire-devel] Fwd: Module packaging, distribution, and management

[Matthew Talbert]

> Or you could simply choose to install modules which are never going to
> be available in Debian. Including licence reasons. As a Farsi user there
> are no PD files for me.

Using "suggests" rather than recommend would prevent any package
manager from automatically installing anything, leaving you to use the
module manager to install whatever you liked.

> I would think that module files growing from 2mb (a complete bible) to
> something like 9-10mb is a bandwith concern.

9-10mb compressed would not happen with any modules I've looked at.
Most would be far less. KJV uncompressed with indices is 8.5MB and
that's a large one. FarsiOPV is 6.0MB uncompressed.  For all of the
modules together, adding the indices would only add a fraction of the
total.

> Please also do not forget that jsword and sword use different
> implementations for lucene.

The indices would be usable via libsword (which is still what we're
discussing here, unless my recommendation to suggest the modules for
the front-ends is taken) and GnomeSword. BibleTime I believe also uses
its own indexing scheme.

> In consequence, if we ever want to package jsword (and why not since
> Java has gone the F/LOSS way?) and Bibledesktop or Kiyut, we would have
> to distribute module files with two kind of indeces.

I don't think we would *have* to, necessarily. If we would combine
Jonathan Mardsen's suggestion of providing a utility to do indexing
correctly with mine to make the modules linked to the frontends, then
each frontend could provide a utility that could do indexing at
install time.

Of course, I think it would be preferable to just let each front-end
worry about installing the modules and indices as each one sees fit.

Matthew