Chris Little wrote: > DM Smith wrote: >> Chris/Troy, >> >> Can we please actually add this to the conf's. I think it becomes >> important for larger modules, so perhaps, we say that the default for >> the entry is <2M? (or whatever would be about 15 minutes on dialup) I >> don't see any reason that it needs to be highly accurate. The nearest >> K or even 100K should be sufficient. That is a minor change to the >> module would not warrant re-computation. >> >> It is so easy to script and automate and our conf's rarely change. >> >> For compressed modules, this is nearly the same as the download size. >> For uncompressed modules, even if we do ftp compression on the fly, it >> is still a good measure of transit time. > > I would imagine this is something Troy should install on the server. I > don't have any objection. I just thinks it's a server admin matter to > install the script. > > --Chris >
This is an ancient thread which - after running a year or so is ending in a fade out. The agreement appears to have been there. But the implementatio is not. It has come up again during the wiki comparison - that some applications laboriously calculate install size and warn while it would be nice and easy if this info was provided as a part of the module configuration file. I am running a tiny netbook with small "harddrive" flash thing. So install size is suddenly again quite crucial. Peter _______________________________________________ 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
