1] clk dwnl’d icon…
2] clk icon - grn box…
3] …?
Here you go again. No background (e.g., OS - only looking into your other (likewise badly asked) questions gives a hint it’s Windows), a cypher instead of normally written words, no sign of respect to those who are willing to answer. I hope this (and other likewise bad) questions of you won’t be answered until you learn how to ask questions the smart way.
For Window$:
-
Updating from 32-bit LO to 64 or the other way around (which is downgrade and shouldn’t be recommendable) ? Then uninstall the old version first.
-
Otherwise, assuming same main version (LO 3 updates LO 3, 4 updates 4, etc.) just install a newer non-RC and non-beta version in the same folder.
2.1) RC versions generally will update an existing regular or RC but not beta installation just fine.
2.2) Beta versions generally install in parallel, which (generally ?) presents the problem of the beta becoming the LO that’ll be used, in which case the beta has to be uninstalled and the regular/RC repaired to return to before the beta. In both cases the release notes for a new pre-release will tell if there’s something to know before installing.
For Linux, BSD and the like:
-
If your distro uses central package management (for ex. Debian[-based]), just update through it. Note: at least on Ubuntu the RC versions are given the same as regular versions (no distinction), but separated in their own repos.
-
I imagine source-based is updated by
configureing andsudo make installing a new source, but that’s just how I think it goes since I’ve never done it.
For Mac:
I imagine Mac is combination of Window$ and NIX: you run a package downloaded from the site and the software is updated in place.