<html><head></head><body>Thank you, Troy!<br>
Ok, I didn't see that there are these entirely different use cases when constructing a SWMgr instance. I created my own factory method and basically tried to use the same kind of SWMgr object both for installing/uninstalling and for reading the content of modules.<br>
I think the API docs could mention those different use cases.<br>
<br>
For the parameter iConfigPath it says:<br>
iConfigPath provide a custom path to use for module set location, instead of searching the system for it.<br>
<br>
I think here it should say something at least about 2 different use cases:<br>
1) Installing/ uninstalling<br>
2) Reading module information/content<br>
<br>
Currently the description only applies to the second use case.<br>
<br>
Best regards,<br>
Tobias<br><br><div class="gmail_quote">Am 8. Juli 2019 13:33:42 MESZ schrieb "Troy A. Griffitts" <scribe@crosswire.org>:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Yes. This is expected behavior. If you sudo your installmgr command, it will have access to install globally. If you cd to your ~/.sword folder and run the installmgr command, it will install to the CWD (as long as a mods.d/ folder exists to let SWORD know you are at the root of a SWORD module library).<br><br>Programmatically, you should specify where you want to install (globally or to a private module library for the user), so you are exactly correct. You should provide a destMgr which specifies the installation location. There are means to query an SWMgr which has autodiscovered its module library. Maybe you could see if you have write permission to the path.<br><br>Troy<br><br><div class="gmail_quote">On July 7, 2019 11:35:16 PM MST, Tobias Klein <contact@tklein.info> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi,<br><br>I'm struggling with some basic issues regarding installation of modules.<br><br>When using a SWMgr that has been initialized with no arguments as a <br>destMgr (first Parameter) for InstallMgr, my module installs fail.<br><br>Same thing happens when trying to use the command line utility installmgr:<br><br>./installmgr -ri CrossWire KJV<br><br>...<br><br>...<br><br>Error installing module: [KJV] (write permissions?)<br><br><br>On the other hand if I use a SWMgr with a fixed path as the first <br>parameter (for example pointing to ~/.sword) then the installations of <br>modules are succeeding.<br><br>I'm using Sword 1.8.1.<br><br>Best regards,<br>Tobias<hr>sword-devel mailing list: sword-devel@crosswire.org<br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page<br></pre></blockquote></div></blockquote></div><br>
-- <br>
Message sent from my phone. Please excuse brevity.</body></html>