Quote:
Originally Posted by TonyToews
I did a search in the bug database. The two or three bugs mentioning this problem were closed. One blaming Microsoft which I find hard to believe. (Don't get me wrong, Microsoft have lots of things to be blamed for. <smile>) Even one or two seconds is excessive. As far as I'm concerned this is a bug but clearly no one wants to take a look at the problem.
|
Well, Microsoft
is to blame, believe it or not. And, as mentioned before, a couple of people including a programmer with extensive knowledge of the installer system have tried to get rid of that. The reason the space requirements are taking so long is that the installer is optimized for executable files and DLLs, not Python files. The files normally packaged in an installer package contain a checksum of their contents for the purpose of quickly detecting changes, the many Python and other files Calibre brings don't. Thus, the installer has to generate checksums of not only the files it contains, but also the entire Calibre directory to see which files have changed. This is, as you surely would point out, unnecessary, since you could just go ahead and overwrite everything, but, as it turns out, it's impossible to turn off that behaviour. So, your options are either to do something about it (although I couldn't say what one could do) or just deal with it.
Generally, if a ticket indicates that the bug won't be fixed, it's either for some technical reason like above or because it comes from a design decision that won't change (or won't change anytime soon). If you wish to know the reason behind it, a search in this forum should unearth the relevant thread(s). Were I a developer, I'd be pretty annoyed if people showed up out of thin air and concluded, that, since their pet bug won't be fixed, clearly nobody is interested in doing so.