gapan wrote:Also, upgrading the firefox package to the newer one when that becomes available will most probably leave files that do not belong to any package and might create conflicts.
thenktor wrote:gapan wrote:Also, upgrading the firefox package to the newer one when that becomes available will most probably leave files that do not belong to any package and might create conflicts.
I've thought exactly the same on first thought. Probably it's no problem, but still I would stick to official Slackware/Salix packages.
http://szone.berlinwall.org/node/105 wrote:Disabling Application Updates In the firefox.js there is a line that looks like this: pref("app.update.enabled", true); Change that to: pref("app.update.enabled", false); and then your clients will not check for updates automatically.
1 diff -up mozilla-1.9.2/browser/base/content/utilityOverlay.js.checkForUpdates mozilla-1.9.2/browser/base/content/utilityOverlay.js
2 --- mozilla-1.9.2/browser/base/content/utilityOverlay.js.checkForUpdates 2010-06-13 15:36:16.617677299 -0700
3 +++ mozilla-1.9.2/browser/base/content/utilityOverlay.js 2010-06-13 15:39:54.485387418 -0700
4 @@ -510,7 +510,7 @@ function buildHelpMenu()
5 // Disable the UI if the update enabled pref has been locked by the
6 // administrator or if we cannot update for some other reason
7 var checkForUpdates = document.getElementById("checkForUpdates");
8 - var canCheckForUpdates = updates.canCheckForUpdates;
9 + var canCheckForUpdates = updates.canCheckForUpdates && updates.canApplyUpdates;
10 checkForUpdates.setAttribute("disabled", !canCheckForUpdates);
11 if (!canCheckForUpdates)