Plugin:PluginUpdater/en: Difference between revisions

From Miranda NG
Plugin:PluginUpdater/en
Jump to navigation Jump to search
(Translated)
No edit summary
Line 5: Line 5:
| dll=PluginUpdater.dll
| dll=PluginUpdater.dll
}}{{Languages}}
}}{{Languages}}
Plugin updater for Miranda NG.
Plugin updater for Miranda NG. It compares hashes of the installed plugins with those on the server and if they differ, downloads archived updates and replaces the local copy.


== Tips and Tricks ==
== Tips and Tricks ==
# There are no any checking of dates and version of the plugins. So if you have compiled yourself or got anywhere newer version of the plugin PluginUpdater does download it from the server, even if it is "older". This behaviour was made consciously to exclude user`s problems with unknown sourced plugins.
# It should be noted that PluginUpdater doesn't check plugins' versions nor their compilation dates. So if you compile a plugin by yourself (or somebody does and shares it with you), PluginUpdater will still download its "older" version from the server. This was done on purpose to avoid problems with plugins from doubtful sources.
# Plugin hashes are computed by special algorithm to exclude compilation time of the dll, which is included into the dll. So if a plugin is compiled with one compiller from the same sources in differ time it has the same hash for PluginUpdater but different hashes for standard MD5 utils.
# Special algorithm for calculating plugins' hashes ignores information about DLL compilation time (which is also written to DLL). Thus a plugin compiled from the same source code with the same compiler but at different time will have the same hash for PluginUpdater but different one for ordinary MD5 calculation tools.
# The plugin is tuned in to checking [[Stable Version]] of Miranda. So it is possible when the plugin rolls away fresh [[Unstable version]] of Miranda. '''This is not a mistake''' and can be tuned into the preferences.
# By default PluginUpdater is set to check updates for the [[Stable version]] of Miranda. So it is likely to rollback your latest [[Development version]] of Miranda to stable one. This is '''not a bug''', navigate to Options… → Services → Plugin Updater and choose the option you prefer.
# '''For packs-makers:''' It is possible to set your own URL to check updates. You became responsible for opportune updating of the plugins store.
# If you distribute '''your own''' Miranda Pack, you can select "Custom version" option and set your URL for PluginUpdater to download updates from. In this case you become responsible for keeping your repository of plugins up-to-date.
# If you set key {{DBKey|PluginUpdater|RestartCurrentProfile|0}} the plugin will restart Miranda to [[Profile manager]] ({{Rev|3346|revision 3346}}). The plugin restarts Miranda to current profile by default.
# If you set the key of <tt>BYTE</tt> type {{DBKey|PluginUpdater|RestartCurrentProfile|0}}, the plugin will restart Miranda to [[Profile manager]] ({{Rev|3346|revision 3346}}). PluginUpdater restarts Miranda to current profile by default.


[[Category:Utils]]
[[Category:Utils]]
[[Category:Services]]
[[Category:Services]]

Revision as of 00:40, 1 February 2013

Template:PluginCard/en

Plugin updater for Miranda NG. It compares hashes of the installed plugins with those on the server and if they differ, downloads archived updates and replaces the local copy.

Tips and Tricks

  1. It should be noted that PluginUpdater doesn't check plugins' versions nor their compilation dates. So if you compile a plugin by yourself (or somebody does and shares it with you), PluginUpdater will still download its "older" version from the server. This was done on purpose to avoid problems with plugins from doubtful sources.
  2. Special algorithm for calculating plugins' hashes ignores information about DLL compilation time (which is also written to DLL). Thus a plugin compiled from the same source code with the same compiler but at different time will have the same hash for PluginUpdater but different one for ordinary MD5 calculation tools.
  3. By default PluginUpdater is set to check updates for the Stable version of Miranda. So it is likely to rollback your latest Development version of Miranda to stable one. This is not a bug, navigate to Options… → Services → Plugin Updater and choose the option you prefer.
  4. If you distribute your own Miranda Pack, you can select "Custom version" option and set your URL for PluginUpdater to download updates from. In this case you become responsible for keeping your repository of plugins up-to-date.
  5. If you set the key of BYTE type PluginUpdater/RestartCurrentProfile = 0, the plugin will restart Miranda to Profile manager (revision 3346). PluginUpdater restarts Miranda to current profile by default.
Retrieved from "https://wiki.miranda-ng.org/index.php?title=Plugin:PluginUpdater/en&oldid=745"