>> 3. Allow installing a zipped module. That is, the library would unzip
>> it itself and install it somewhere. This would be useful for all of
>> the frontends I think, and it's best to handle it in SWORD, because it
>> already has the necessary functionality to do this (very similar to
>> the unt
Matthew Talbert wrote:
> specifically that I would like to see:
>
> 1. HTTP support. This is planned.
Interfaces and shell classes already in place. Just need someone to
implement.
> 2. Allow specifying the location of where to install modules. This is
> quite simple and I could easily do it,
> OK. Without that, it's not clear to me how usable a central shared location
> really is -- either you have to run your big GUI app as root to install
> modules to it (awkward, and potentially dangerous), or you make the shared
> location writeable by everyone (and risk accidental deletions),
Matthew Talbert wrote:
So Xiphos now prompts for root privs when needed, so it can write
shared modules to /usr/share/sword/ ? Nice, I'll have to try it
out!
No, it only tests to see if the user has permissions to install
there. If they do, then it is offered as an option. If not, it is not
s
> Further, in the case of the install locations, once a couple of apps "do
> their own thing", there may well be lowered interest -- library developers
> may then "assume" that app developers have no interest in this functionality
> being in the library!
>
> Rather than people on either side of the
Matthew Talbert wrote:
My point wasn't about localization really, just wanted to point out
that SWORD_PATH is more far-reaching than simply a way to change where
modules get installed.
OK, but if you only ever use SWORD_PATH in a script that calls
installmgr, then that is the only effect it h
> Maybe, but there are reasons that those applications which strive to
> be cross-platform do a lot of those things themselves. In order to
> support paths with non-ASCII characters, each OS seems to have a
> different proper way of doing this. At least on Win32 the only method
> I'm aware of is
> 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
>
On Thu, Sep 3, 2009 at 2:29 PM, Jonathan Marsden wrote:
> 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
>> l
Troy,
On Tue, Sep 1, 2009 at 8:38 PM, Greg Hellings wrote:
> Troy,
>
> You may not be thinking of me in particular, but I have brought that
> up before. I thought about the SWORD_PATH issue after I ran diatheke
> the first time, and it failed. So I set SWORD_PATH, and tried running
> installmgr
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
>
>> One more thing. If the last step in building sword is "make config", then
>> there is no reason to set SWORD_PATH at all. (even if it isn't the last
>> step, there's no reason to, I think). SWORD will automatically look in
>> ~/.sword and whatever paths are set in /etc/sword.conf without needi
Matthew Talbert wrote:
One more thing. If the last step in building sword is "make config",
then there is no reason to set SWORD_PATH at all. (even if it isn't
the last step, there's no reason to, I think). SWORD will
automatically look in ~/.sword and whatever paths are set in
/etc/sword.con
One more thing. If the last step in building sword is "make config",
then there is no reason to set SWORD_PATH at all. (even if it isn't
the last step, there's no reason to, I think). SWORD will
automatically look in ~/.sword and whatever paths are set in
/etc/sword.conf without needing SWORD_PATH
> mkdir -p $SWORD_PATH/mods.d
> The need for the mkdir -p command seems odd to me, because -init "sounds
> like" it should initialize the data area for me, including creating
> whatever subdirectories it needs. But without that mkdir -p, or if I
> rfeplace it with mkdir -p $SWORD_PATH , the sequ
Greg Hellings wrote:
> You may not be thinking of me in particular, but I have brought that
> up before. I thought about the SWORD_PATH issue after I ran
> diatheke the first time, and it failed. So I set SWORD_PATH, and
> tried running installmgr again, and it continued the fail with the
> same
Troy,
You may not be thinking of me in particular, but I have brought that
up before. I thought about the SWORD_PATH issue after I ran diatheke
the first time, and it failed. So I set SWORD_PATH, and tried running
installmgr again, and it continued the fail with the same error. I
also tried wit
Dear Greg,
Someone reported on IRC #sword to me (I thought it might have been you)
that SWORD 1.6.0 does not error out if it cannot determine your SWORD
module library path.
This was your first problem: you set SWORD_PATH _after_ you ran installmgr.
svn head should now error out if SWORD isn
I just installed SWORD 1.6.0 from tarball onto another fresh (Linux
Mint 7 - a derivative of Ubuntu) system.
I built as a regular user (greg), installed with sudo make install.
I ran sudo installmgr -sc
Then sudo installmgr -ri CrossWire KJV with output:
Installed module: [KJV]
Then export SWO
I just installed SWORD 1.6.0 from tarball onto another fresh system.
I built as a regular user (greg), installed with sudo make install.
I ran sudo installmgr -sc
Then sudo installmgr -ri CrossWire KJV with output:
Installed module: [KJV]
Then export SWORD_PATH=/usr/local/share/sword
Everythi
I just installed SWORD 1.6.0 from tarball onto another fresh system.
I built as a regular user (greg), installed with sudo make install.
I ran sudo installmgr -sc
Then sudo installmgr -ri CrossWire KJV with output:
Installed module: [KJV]
Then export SWORD_PATH=/usr/local/share/sword
Everythi
21 matches
Mail list logo
