Quote:
Originally Posted by dunhill
Exactly. The plugin checks the OS but relies on the user having a standard installation. I've added a clear warning in the confirmation dialog stating that Portable, Flatpak, and AppImage versions are not supported and must be updated manually.
Since those versions don't follow the standard Windows Registry paths for the .msi installer, trying to automate them would lead to the 'Retry/Ignore' errors you mentioned. Keeping it restricted to official standard installs is the safest way to avoid corrupting a user's setup.
|
Please read what I actually wrote; it's about what is running when the
msi installer is started, nothing to do with installing portable itself.
I've attached some screenshots - the executables that the portable launchers start are identical to the installed calibre executables, the difference is that they're loaded from a different location and some variables are set to precondition the execution environment.
I have no idea if that is relevant to your plugin. Knowing you don't use Windows, I wanted to make sure that you were aware that the msi installer will not run to completion if any of the calibre executables are running from a portable install.
Added: Perhaps you're not aware that 'installed calibre' and multiple copies of 'calibre portable' can coexist on the same Windows system.
BR