[Pkg-crosswire-devel] Module dependencies

Matthew Talbert ransom1982 at gmail.com
Mon Jan 26 17:08:14 GMT 2009


>> The applications don't know how the modules have been installed, they
>> just see them through the Sword API. After the modules have been
>> installed with a package manager or a Sword installer they are just
>> ordinary files to the Sword. If a Sword app is run as root it can
>> uninstall the files in any case (which may leave the package
>> management system in a broken state).
>
> Thanks for the info!  I believe that this means that the functionality
> which I think is needed is not implemented yet.

I know you said we could discuss this at a later date, but roughly how
would you propose that the two systems cooperate?

> I think that the logical consequence of this is that the libsword7
> package which we're currently building should *conflict* with all
> module packages that we know of (forcing any such packages which are
> currently installed to be removed).

Of course, users may not like their modules to suddenly disappear. Is
there a way to leave the actual modules there, but remove the package?
Failing that, is there a way to notify the user to use his front-end
to re-install the Bibles (a note suggesting that the modules available
are probably newer than what he had might be helpful as well).

> For future revisions of the sword package, I believe that we should
> discuss with the upstream developers how a more sane solution can be
> reasonably achieved, but that discussion can IMO be delayed until the
> more urgent packaging issues are resolved.

I completely agree with this. I believe we have gotten side-tracked on
this issue, when I think what we all really want is updated packages
in Debian/Ubuntu before the approaching cut-off date. I would like to
see us all work together to accomplish that.

Matthew




More information about the Pkg-crosswire-devel mailing list