Difference between revisions of "Talk:Firefox"
(→Check for file version) |
|||
| Line 29: | Line 29: | ||
When checking the uninstall string, it'll perform a downgrade if the version installed on the client is newer than the one distributed by WPKG. | When checking the uninstall string, it'll perform a downgrade if the version installed on the client is newer than the one distributed by WPKG. | ||
| + | |||
| + | :: Isn't our assumption in this wiki that we're in a 'WPKG world' where application updates are managed by WPKG, so the apps installed on a workstation will always be the same or older than those in WPKG? | ||
| + | (and in some environments you potentially also even want newer versions downgraded to the WPKG packaged version so that all apps in the organisation are at the same revision, for better IT support through consistency) | ||
Revision as of 18:02, 24 November 2008
Don't you think it's time to clean a little this article - it's getting messy here.
- Hmm, yeah, why not - what do you propose to change? Or just change it.
- Well, we could move extensions installation to a new single thread and live just FF v1/2/3 packages. Or even get rid of FF2, because everyone who'd like to install v2 should use v3, and if someone has an old computer might have want to use v1.5 (but I haven't checked does FF 1.5 works better than FF 2 or FF 3 on old machines)
- What about creating Firefox:Extensions page, and move the extensions there (both pages should link to each other)?
- Well, we could move extensions installation to a new single thread and live just FF v1/2/3 packages. Or even get rid of FF2, because everyone who'd like to install v2 should use v3, and if someone has an old computer might have want to use v1.5 (but I haven't checked does FF 1.5 works better than FF 2 or FF 3 on old machines)
- Hmm, yeah, why not - what do you propose to change? Or just change it.
Exactly!
- So do it! ;)
- I recommend having sections for each version that there is info on the page for, not throwing away the knowledge gained in this wiki. Though I also recommend getting rid of info on especially old versions that are completely outdated, such as Firefox 1.0. I don;t think people here should be making judgements such as "because everyone who'd like to install v2 should use v3" - the systems we setup, where an on-site admin might continue to update Firefox 2.x within the remit of their current software suite, but not have the ability to move to our new suite with Firefox 3 yet, can keep going with 2.x until the time is right; people here shouldn't be supposing they know when precisely people are able to upgrade, when we're only talking about the previous major release series.
Check for file version
Why are you having it check for the existence of the uninstaller? Checking firefox.exe's version would be more convenient. Obviously, firefox.exe's version number does not represent the Firefox version (e.g. 3.0.4), but the Gecko version (e.g. 1.9.0.3224). So instead of
<check type="uninstall" condition="exists" path="Mozilla Firefox (3.0.4)" />
we could have
<check type="file" condition="versiongreaterorequal" path="%PROGRAMFILES%\Mozilla Firefox\firefox.exe" value="1.9.0.3224"/>
Here are the Gecko versions of some other releases: 2.0.0.17 1.8.20080.17373 2.0.0.18 1.8.20081.2918 3.0.4 1.9.0.3224 3.1b1 1.9.1.3202
- Why not check the uninstall string?: <check type="uninstall" condition="exists" path="Mozilla Firefox (3.0.3)"/>
When checking the uninstall string, it'll perform a downgrade if the version installed on the client is newer than the one distributed by WPKG.
- Isn't our assumption in this wiki that we're in a 'WPKG world' where application updates are managed by WPKG, so the apps installed on a workstation will always be the same or older than those in WPKG?
(and in some environments you potentially also even want newer versions downgraded to the WPKG packaged version so that all apps in the organisation are at the same revision, for better IT support through consistency)