>> On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings <[email protected]> >> wrote:
> It should. It does not. AFAIK it currently maintains no status > information on whether ABC came from site X, site Y, a local install > file, or was manually inserted into the install location. Since > modules are just a collection of files on a disk bound together by a > conf file, there is no way of preventing a user from unzipping a > module she received in email into the folder. If that module is named > ABC then InstallMgr will assume it is the same module as ABC from > source X and offer an upgrade if the local version is less than site > X's version. I think it does - here's how I think it does. In Linux at least, it seems to track version numbers in the .conf file. For example, I have an Inuktitut sword module whose version information is kept locally here: ~/.sword/InstallMgr/20120224005250/mods.d/ink.conf The 20120224005250 bit seems to be explained in InstallMgr.conf as being specific to a particular site. [General] PassiveFTP=true [Sources] FTPSource=1XO|x.xxx.xxx|/pub/sword/raw|||20120224005250 <CUT> How I understand this then is that InstallMgr writes information about modules in the form of .conf files (in my case ink.conf) to the 20120224005250 directory. If there's a difference between the .conf file in the 20120224005250 and the .conf file in the site associated with 20120224005250 it means there's an update. Thus, when you install from a different source InstallMgr could see that you have a .conf file for that module (INK for example) (in your InstallMgr directory or subdirectory) delete it and put the new copy in a source directory from which it was downloaded establishing a link between the most recent download and the module. ~A _______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
