View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002373||SUMo||New Feature||public||2013-12-06 10:28||2019-05-16 19:36|
|Target Version||Fixed in Version|
|Summary||0002373: Reporting when multiple versions of same product installed|
|Description|| Some applications might -- during their update process to newer versions -- leave older modules behind (sometimes, even the main module, as the newer one has a different name).|
Regretfully, while the most up-to-date version might be installed, SUMO continues to "nag" that updates are available, because it also sees some of the previous modules on the machine.
It would be nice to apply the same "clean-up" methodology that Secunia's PSI (2.x and possibly 3.x) does, according to which an update suggestion is offered only when no copy of the most up-to-date version is found on the machine being scanned (not only if older modules are found).
To deal with the fact in some cases it is beneficial to report on all versions installed on the machine, maybe an option could be added, to let SUMO "know" how to behave (similar to the "Do not report Betas)
|Tags||No tags attached.|
||I observe the same behaviour. These are hence currently false positives and hence confusing. But ignoring them is not a good idea as they may need other action (not update but cleanup by other tools). So for standard use case, suppressing this kind of info leads to less confusion. But creating such a report of orphaned predecessors shall remain possible. Hence I prefer a configuration option with ignoring being the standard behavior and reporting intended for advanced users.|
||What about "delete" function ? Why wouldn't you use "Ignore" ?|
What do you mean by delete function?
Do you mean to delete files as a method for cleanup?
Often this is a bad idea as those components are often necessary for a certain feature of the installed package. And SUMO does not yet report directly the relationship of installed application and installed component. So deleting would remove a subset of features of the installed package. And if the component is essential for basic features, the application might be rendered unusable.
And most installers on my system don't provide a repair mode. Even if the installer software would be able to support such a mode, many software publishers don't make use of this feature and operation mode.
I don't like ignore in SUMO as I want to know the details, relationships, existence and many more meta data. And as far as I understood, ignore is currently a very coarse grained configuration option with further tuning options in the development backlog.
And it makes a difference if a component is not updated although should have been by performing the update installation, i.e. because it was in use on that time and the installer didn't require to stop the application first, or because it is no longer needed. SUMO does not provide corresponding information. And it seems to me that often an application may work properly with several predecessor versions of components. I can imagine that some software publishers don't know the installer software and features not well enough and resulting in a different configuration set if updating or if installing freshly, not by design but by lack of knowledge. For such cases data backup, uninstall and reinstall can be a remediation resp. cleanup method, not delete nore ignore as action is needed.
||"Delete" removes item from the list but do NOT delete any file on the user's system.|
|2013-12-06 10:28||trattner||New Issue|
|2013-12-08 20:44||Kyle_Katarn||Assigned To||=> Kyle_Katarn|
|2013-12-08 20:44||Kyle_Katarn||Status||new => acknowledged|
|2019-04-15 22:40||wolf||Note Added: 0003218|
|2019-04-17 21:43||Kyle_Katarn||Note Added: 0003227|
|2019-04-21 17:51||wolf||Note Added: 0003241|
|2019-04-21 22:51||Kyle_Katarn||Note Added: 0003244|