Title: signature
Thank you, DM. I have (I hope) automated the zip cache maintenance, forcing case and zip file consistency.

By the way, I think use of HTTP instead of anonymous FTP is a good idea for the future, for all front ends, as the gradual shift from IPv4 to IPv6 marches onward. I had to disable IPv6 on eBible.org to make the repository work. I don't particularly like that work-around, and don't consider it to be permanent. IPv6 will be turned on for eBible.org, again. At that point, the HTTP repository will still work on eBible.org, but we may have to move IPv4-only anonymous FTP access to another domain or subdomain, probably ftp.ebible.org.

Therefore, it is probably better to shift to listing the eBible.org FTP repository to use the host name ftp.eBible.org instead of just the simpler-to-type eBible.org. Right now, they resolve exactly the same, but this will change once I figure out how to turn IPv6 support back on for just plain eBible.org without harming my email or web access. (This will probably involve a change of DNS service provider, which, in turn, affects my email.)


On 08/10/2015 11:02 AM, DM Smith wrote:
Many thanks for your work. It is a great kingdom blessing.

Historically, CrossWire has maintained zips as cache of the modules as individuals download them via a jsp program. The zips are named according to the contents of the conf’s section name (i.e. what’s between the [ ] on the first line of the conf). JSword took advantage of those downloads as a more reliable transport. First it was via FTP but as FTP in ancient Java (aka 1.4) proved un-reliable on Windows, that was abandoned in favor of http. (I’m working on adding FTP back in, but that is a different story.)

The upshot is that zips need to have the same casing as the section name.

I’m attaching a script which I use to help maintain the consistency of the various repositories at CrossWire. Here is a general overview. The program makes the assumption that the conf files, zips and module files all must be present. It crosschecks these. If the conf does not exist for a module, the module files are marked for deletion. If the conf exists but the module files do not then the conf is marked for deletion. If a zip does not match the section name of a conf then it is marked for deletion.

The other thing that the script does is maintain InstallSize in the conf. If it is not there, it’ll add it. If it is there, it’ll verify that the value is right.

If a zip does not have the right casing, it is marked for delete. (I probably should change the program to report/fix the problem.) If a zip with the right casing does not exist it is created. 

The -n argument allows for a report of what would happen. The -k option will do the deletion, and it will ignore the -n.

The program does it’s work by reading the conf for the section name, the data path and install size, building various maps to do its work.

Right now I run it by hand. Which is good if a conf or the module files are accidentally deleted and the zip is all that is left to restore the module.

In Him,
DM Smith




On Aug 10, 2015, at 3:52 PM, Kahunapule Michael Johnson <kahunap...@ebible.org> wrote:

It appears that I need to be consistent, and use the mixed caps for every reference to the module name, including file names and directory names. To do that, I am going to rebuild the repository, which will take about 24 hours. A refresh of the repository after that will be needed.

Note that I can't do anything in the repository about capitalization of path names above "modules", so the capitalization issues with Application Data\Sword come from somewhere else.


On 08/10/2015 06:02 AM, Michael H wrote:
On BibleDesktop (1.6) running on Windows 7 professional (in a Parallels environment on top of Mac OSX Yosemite): 

1. eng_t4t2014: "The given URL C:\Users\me\Application Data\Sword\modules\texts\ztext\eng_t4t2014 could not be created as a directory." Browsing with a file manager shows "application data" and "sword" are not capitalized. appears to be affecting all modules from ebible.org. I've randomly installed from other repos no issues. 

2. engBBE1964 : "The Bible in Basic English is 0kb, continue install?", "Unable to find: Not Found:/sword/zip/engBBE1964.zip." Capitals appear in error: Internet explorer browsing the zip directory on ebible.org via http shows all characters lowercase. 


On Sun, Aug 9, 2015 at 12:23 PM, Kahunapule Michael Johnson <kahunap...@ebible.org> wrote:
The new Sword repository at ftp://eBible.org/pub/sword and http://eBible.org/sword is now ready for testing. Please let me know if there are any more opportunities for improvement in the repository. Any action to make sure front ends are compatible would be appreciated. Thanks for the Xiphos crash fix. I hope it gets packaged and rolled out, soon, through all of its distribution channels.

--
Your partner in electronic Bible publishing,

MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143

USA
eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Reply via email to