<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The repo admin needs to decide what is best for all users of the repo.<div><br></div><div>For example, they cannot assume that Xiphos (to pick out one SWORD application) is the same version for every user. And even if it is the same version, they cannot assume that lucene is the same. So, having the indexes in a public repo is a bad idea. In a private repo, it doesn't matter.</div><div><br></div><div>To repeat earlier threads of what can cause indices to become invalid:</div><div>New version of Unicode. For JSword, this is based upon the version of Java. A Java upgrade requires indices to be rebuilt. (Note: JSword and SWORD cannot share indices.) For Windows, I think it is part of the OS. If so XP, Vista, Win 7 and Win 8 clients may have different Unicode. The same idea applies to Linux.</div><div><br></div><div>To the extent that ICU is used to provide Unicode, the same applies. The app can be compiled w or w/o ICU.</div><div><br></div><div>The version of the SWORD lib has to be the same.</div><div><br></div><div>The version of Lucene has to be the same.</div><div><br></div><div>There is no mechanism in SWORD or JSword to know when an index is not valid and in need of being rebuilt.</div><div><br></div><div>Short of an application having tight control over the index (such as PocketSword, AndBible and STEP) it does not make sense to have indices stored in the repo. Even then, the indices should be stored in parallel, not with the module.</div><div><br></div><div>The only reason I see to have it otherwise is if the repo is private and personal.</div><div><br></div><div>Hope this clarifies.</div><div><br></div><div>In Him,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div><div><br></div><div><br><div><div>On Jan 23, 2013, at 12:52 PM, Andrew Thule <<a href="mailto:thulester@gmail.com">thulester@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="">Peter, DM, </span><span style="">Thanks for your response. </span><span style="">I </span><span style="">wasn't being critical and I agree. T</span><span style="">here are Pros and Cons either way (resource usage and download time being considerations) as you point out.</span><div>
<div><span style=""><br></span></div><div><span style="">I also agree it's ultimately it's up to the repo administrator and the user, to decide for themselves what works best for them. </span><span style="">I happen to like having the index included as part of the repo, because I'm not limited by resources, and I don't mind the wait.</span></div>
<div><span style=""><br></span></div><div><span style=""></span><span style="">Regardless, </span><span style="">it is still a</span><span style=""> m</span><span style="">atter of preference (based upon considerations, such as the ones you cite).</span></div>
<div><span style="">~A<span></span></span></div><div><br>On Wednesday, January 23, 2013, DM Smith wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On Jan 23, 2013, at 11:02 AM, "Peter von Kaehne" <<a href="javascript:;" onclick="_e(event, 'cvml', 'refdoc@gmx.net')">refdoc@gmx.net</a>> wrote:<br>
<br>
><br>
>> Von: Andrew Thule <<a href="javascript:;" onclick="_e(event, 'cvml', 'thulester@gmail.com')">thulester@gmail.com</a>><br>
><br>
>> The nice thing about when<br>
>> repo administrators do this, is when you get a module from that repo, you<br>
>> also automatically get the lucene index.<br>
><br>
> The reason that this is not done are manifold - including that sword and jsword indices are different, that not all platforms have the same lucene/clucene incarnation etc.<br>
><br>
> Most users are better off not to use downloaded indices, but to create indices suitable for their specific frontend.<br>
<br>
To add to what Peter said, this mailing list's archives have extensive discussion on why we don't do this and why we have done it for mobile devices (only PocketSword and AndBible, and specific to them only).<br>
<br>
Also, the transfer time for a lucene index exceeds the time of a recent computer to build them, e.g. my laptop. As a Bible Desktop user, I'd really rather not transfer an index that is unusable by Bible Desktop.<br>
<br>
In Him,<br>
DM<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="javascript:;" onclick="_e(event, 'cvml', 'sword-devel@crosswire.org')">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote></div></div>
_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><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</blockquote></div><br></div></body></html>