Could it be as it appears that ungoogled-chromium lacks auto-update support? #2740
Replies: 1 comment
-
Incorrect This feature is very platform dependent and on Windows ungoogled-chromium follows Chromium closely. On Linux however this feature is often implemented by a package manager instead.
There is no such functionality in ungoogled-chromium, but fortunately @claudiodekker created https://github.com/claudiodekker/chromium-update-notifier which might be fitting for your needs. I haven't used it so cannot suggest or give advices on it. Also I should mention that it is developed independently from ungoogled-chromium and in no way related to it. |
Beta Was this translation helpful? Give feedback.
-
Good morning. I was able to draw from my own experience the conclusion that this browser in stable version for Windows 64-bit (tested: variant 11, version 23H2) lacks auto-update support. I was able to see that this was also the case with the Chromium code, for Windows 64-bit, through an acquisition at the source https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/ of a portable type archive, for example that for the 1267524-build corresponds to the relative path 1267524/chrome-win.zip. However, the files from this source represent without exception developer type versions, which are here at https://www.chromium.org/getting-involved/download-chromium/ explicitly presented as being devoid of auto-updating support.
This browser, although presented as close to Chromium in terms of code, is nonetheless unique in its differences. Anyone who, like me, discovers this browser, can reasonably assume that auto-update support has been introduced, this being of undeniable convenience. However at https://ungoogled-software.github.io/ungoogled-chromium-wiki/faq, which is the place where we are entitled to see a question asked relating to this support, we surprisingly see its absence. Neither does the README.md file mention the introduction of such support in this browser.
Could it be that such support exists but is disabled by a flag? It seems inconceivable these days to be put in the position of having to watch for the release of a new version, for example via the built-in function of this platform known as Watch, in order to manually acquire it, and proceed with its extraction or installation.
Beta Was this translation helpful? Give feedback.
All reactions