[Pkg-crosswire-devel] Packaging Sword modules

Norbert Bollow nb at bollow.ch
Thu Jan 29 00:04:45 GMT 2009


Peter von Kaehne <refdoc at gmx.net> wrote:

> I am sure there are ways forward beyond this point right now-
> particularly also in the area of custom distributions in particular
> nasty or remote areas of the world, but can we for the moment leave this
> aside? Most of our modules _are_ redistributable (just not fit for
> inclusion in Debian's repos due to  Debian's strict standards on
> freeness) and hence it should be easy to figure out custom distros for
> particular purposes.
> 
> Again, there was no intention to upset, of shooting from the hip or of
> posting cease and desist letters. Acute exasperation at the
> repetitiveness of it all was the background to my terse last post

Many thanks for clarifying this... it certainly feels good to be
reassured that the request is coming from a mindset which is in
fact compatible with the key Kingdom of God principles which I
feared might be getting violated.

In summary (and yes, this is also repetitive, but some degree of
repetitiveness is unavoidable before any kind of consensus can
be reached) I think we should take the following steps:

a) Package current software versions without referring in any way to
   module packages (not even with "Suggests:") and get these updated
   software pachages into Debian and Ubuntu, including backports.

b) Make sure that going forward, new releases of Debian and Ubuntu
   will not contain module packages.  (But don't take any action
   regarding module packages which are already out there, as part
   of already-released distro versions, since for users who have them
   installed already, forcing installed modules to be uninstalled
   automatically would probably be unjustifiably disruptive.)

c) After the more urgent tasks of points 'a' and 'b' are complete,
   work with the upstream developers towards resolution of the
   incompatibility of sword's module package management system with
   the idea of module packages which are installed by a distro's
   package management system.

d) When point 'c' is complete, start providing a module packaging
   script, so that it can be used by anyone who wants to distribute
   modules in package form either locally, or in "nasty or remote
   areas of the world", or otherwise as part of some kind of custom
   distro for a particular purpose.

Blessings and greetings,
Norbert




More information about the Pkg-crosswire-devel mailing list