<div dir="ltr">A live production repository probably shouldn't be the immediate landing place for a developmental script. Can I suggest a 2nd development ebible repository, where untested modules generated by the script can land to be validated without destroying a known working version?<div><br></div><div><div><div>Main sword repositories currently support a very large number of installs (on the 500,000 - 10,000,000 order of magnitude), on 8-10 programs, across ~30 operating systems. It would be very wise that every module is validated before it goes live onto a main repo, and once a module goes live, it isn't replaced daily or randomly with another untested copy, but only when there is a valid reason to update; and then only after the new version is validated. The dev repo or 'nightly build' can continue to be for those willing to live dangerously or participating in trials of a specific language. When we've validated a module that needs updating actually works, it can be copied over. <div> </div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 20, 2015 at 9:00 PM, Karl Kleinpaste <span dir="ltr"><<a href="mailto:karl@kleinpaste.org" target="_blank">karl@kleinpaste.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<font face="FreeSerif">InstallSize support has evaporated.<br>
<br>
$ pwd<br>
/home/karl/.sword/InstallMgr<br>
$ grep eBible InstallMgr.conf<br>
HTTPSource=eBible|<a href="http://ebible.org" target="_blank">ebible.org</a>|/sword|||20150816130503<br>
$ cd 20150816130503/mods.d/<br>
$ grep 'InstallSize=0$' * | wc -l<br>
678<br>
<br>
You don't test your own repo. You should be doing your own
testing -- I'm merely using Xiphos' module manager, and you could
be doing the same -- instead of only reacting to testing from
others. This is at least Round#5 of How EBible Repo Can Fail and
it's still not right.</font><br>
</div>
<br>_______________________________________________<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" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br></div>