Re: [alpine-devel] [PATCH] testing/sword: add new package
On Wed, Jul 16, 2014 at 4:22 PM, Isaac Dunham <ibid.ag_at_gmail.com> wrote:
> installmgr installs "modules" to a configured location.
> This location is set by DataPath and extended by AddDataPath in the
> [INSTALL] section.
> /etc/sword.conf points it at /usr/share/sword; this is not writeable.
> I'm not aware of any way to point it at a sane default that everyone can use.
> If there are NO config files, it will look for ~/.sword/mods.d, and install
> into ~/.sword/modules.
Why not patch it to prefer ~/.sword/mods.d by default? I could
imagine the upstream developers finding that useful too.
> installmgr won't work right unless it can find mods.conf or a writeable
> mods.d directory in the DataPath.
> If it can figure out where it /should/ put modules, it will run,
> downloading the modules to a per-repository location.
> Then it will move them into location or silently delete them.
> Now I need to figure out what's the right fix.
> I guess installmgr should error out if it can't write somewhere.
> Debian's approach is to require at least one package containing a
> SWORD module.
I don't like this, simply because it's creating a package for some
datafiles, which in this case seems odd to me since installmgr is
One thing we could do is simply have a prompt in the post-install
script saying that you must install the modules you want as root. A
couple of other packages do this when they require post-install
Received on Thu Jul 17 2014 - 00:06:34 GMT