Talk about SyMenu or post suggestions, requests, or how-to questions
How to know when to use builtin update?
|
chef Posts: 47
30/06/2019
|
As a newbee of using SyMenu just for almost 10 days, I still don't know when to use builtin update of "installed" tools as far as this feature exists within. Is it save to always try such a builtin feature if existing, and to proceed in any case when it does not initiate a web browser download resp. abort in case of such web browser download initiation is tried?
And in the latter case, I should instead contact SPS package editor to inform him of new available version. Right?
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
01/07/2019
|
You should never use the build in update feature of a program unless the SPS editor decides that it is so pervasive and reliable that the SPS doesn't have to care about it.
But in these few cases, don't worry, the build in update feature is so pervasive and reliable that the program take initiative and update itself almost within warn you.
Mozilla Firefox is one of these.
|
|
|
link
|
|
chef Posts: 47
01/07/2019
|
Gianluca wrote:
You should never use the build in update feature of a program unless the SPS editor decides that it is so pervasive and reliable that the SPS doesn't have to care about it.
But in these few cases, don't worry, the build in update feature is so pervasive and reliable that the program take initiative and update itself almost within warn you.
Mozilla Firefox is one of these.
If I never should use build in update feature of a program unless the SPS editor decides it is so reliable, how may I know this decision?
Which flag in SPS package manager tells me how the SPS editor has decided?
The case of Mozilla Firefox is the only one reported. And it seems that I accidently found another one where you're the SPS editor and I reported back to you via SPS package manager contact feature. But I couldn't find a corresponding flag if this reported package was already known to be at least currently reliable enough and if you were already aware of published updates as corresponding SPS package editor.
And I didn't experience that the program was taking the initiative. I've performed and initiated the built in update check manually before.
And I know of another tool inside PortableApps and SyMenu Suite which is not yet reliable enough and had opened an issue to the tool author more than a month ago, so even before learning it included in SyMenu. This tool isn't only freeware. It has a dual use license, a professional one and a freeware one, the automatic built in feature being reserved to the professional use. But the authors implementation of portable isn't distinguishing sharply enough to comply strictly enough with common understanding of portable edition. Another typical tool not expected as portable is LibreOffice, at least for full feature set.
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
02/07/2019
|
chef wrote:
If I never should use build in update feature of a program unless the SPS editor decides it is so reliable, how may I know this decision?
Which flag in SPS package manager tells me how the SPS editor has decided?
As a user you don't need to know. If you find and update in the SPS Manager, do the update, otherwise the program will update itself without your intervention.
|
|
|
link
|