View Single Post
Old 04-01-2010, 12:03 AM   #14
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 43,776
Karma: 22666666
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Umm the way microsoft designed their installer technology (which is what calibre uses), means that the uninstaller will always only remove files/registry entries the *installer* creates. The uninstaller knows nothing about data created by the *program*. If you want the uninstaller to remove other data, you have to jump through umpteen hoops. Since they designed things that way, I'm guessing they want people to create uninstallers that work that way.

You say you are a programmer and you still think that leaving files on the filesystem affects performance of the OS???!! Even if that were true (which it isn't) it would indicate a poorly designed OS.

And frankly, creating an uninstaller that removes data created by the program is just plain wrong. The potential that creates for mistakes where the user nukes all their data is just too high.
kovidgoyal is offline   Reply With Quote