That is why I would suggest using a configuration script of some kind.
Users should not have to be root to install Sword, and I assume Sword is
intended to work on a wide variety of platforms, which may have very
different directory hierarchy schemes. Thus it is important for Sword to
robustly
But it looks like our church is going to move to the new ESV
translation and so I would like to make a module out of the
ESV (the software that comes with the Bible is Wordsearch and
the bible modules don't seem to be in STEP format either. So
I have exported the text as Rich Text
I've monitored the two sword discussion groups for a few months but can't
decide if I'm supposed to just send in my bug reports as the main web page
implies or continue searching for this elusive list as a common net
ettiquete. Or should I just throw it in this discussion group as I've seen
done.
I generally lurk and have followed the discussion of improving the
installation of Sword for Linux. I have downloaded and distributed the Sword
CD to many people in the Kansas City area and to missionaries that come
through my church. As a result, I also provide technical support for them.
The
I don't think many people commenting on this subject know how sword data
is located. We allow 4 different ways to specify WHERE the data is
saved.
1) current working directory
2) $SWORD_PATH environment variable
3) /etc/sword.conf: DataPath=
4) $HOME/.sword/
Sword data can be place anywhere
why would he get into trouble? We need to support more than one location anyway
(hard
disk and cdrom) at the minimum. If we don't do that already, it needs fixed.
This is a good comment. I agree that the mechanism to supply location
should be extended to allow MULTIPLE data paths.
This is a good comment. I agree that the mechanism to supply location
should be extended to allow MULTIPLE data paths.
...
I think allowing a ':' separated path, instead of a single location
would be a great addition.
Troy,
do you think it would be good / possible to support paths where
I would like to work on a Java port of the SWORD engine. How would I go
about this?
With these 4 methods of specifying the location of data wouldn't it be
possible to share modules in a multi-booting system, as long as at least one
of those systems could read the others file system? That way you could
install whatever frontend you wanted on each of your operating systems and
it looks like either the the SWORD_PATH or the /etc/sword.conf changes
should help you out. i don't have a multi-os environment to play much
with that.
Dan Blake wrote:
With these 4 methods of specifying the location of data wouldn't it be
possible to share modules in a multi-booting
On Tuesday 12 February 2002 16:01, you wrote:
it looks like either the the SWORD_PATH or the /etc/sword.conf changes
should help you out. i don't have a multi-os environment to play much
with that.
Yes you can just point the sword.conf to your files on your windows drive.
Dan Blake wrote:
Hi there .
On 12 Feb 2002 at 19:41, Martin Gruner wrote:
do you think it would be good / possible to support paths where the modules
are not always available, like cd-rom drives?
PLEASE!
God bless ..Barry
From Barry Drake (The Revd - minister of the Arnold and the
12 matches
Mail list logo
