[sword-devel] More installmgr woes... (need for export SWORD_PATH=~/.sword )
jmarsden at fastmail.fm
Thu Sep 3 12:29:45 MST 2009
Matthew Talbert wrote:
> Note that setting SWORD_PATH is *not* the correct way to install into
> ~/.sword (there isn't a correct way with installmgr, I guess).
> SWORD_PATH does more things than just that, for instance, locales are
> loaded from SWORD_PATH/locales.d, ...
I don't think installmgr is fully localized anyway :) I could just do
without installmgr (use wget to grab the KJV.zip file and unzip -qod
~/.sword/ KJV.zip to install it), for this particular test, but ...
surely this is exactly the kind of task that installmgr is supposed to
do for the user, manage installing modules :)
Also I have a similar script installmod.sh that takes a module name as a
parameter, so I can do installmod.sh WHNU and get the desired result.
I could rework that to just use wget and unzip too, I suppose. It just
seems a bit silly, when installmgr exists for this very purpose.
> For Xiphos, we support installing into ~/.sword if DataPath isn't
> writable. We do this by checking it ourselves, ...
OK. IMO it would have been preferable to get a patch into the
libraries, rather than work around this in just one front end
application. That way, your work and your testing benefits all SWORD
apps, not just the one you are working on (assuming your patch is
accepted, of course!).
> Secondly, it would be really nice to have a method to install to a
> certain directory ...
Maybe, although I suspect that if the library did a better job of
picking the "right" place to install new modules to in the first place,
by distinguishing between readable data paths (for locales, or for
finding existing modules, etc.) and writeable ones (for installing,
updating and deleting modules), then manually specifying an install path
would probably not be necessary.
More information about the sword-devel