@esvignolo, @lainz
Thank you for the feedback. I know the update Column/Button is somewhat confusing. Initially, I only wanted a central repository + a tool to easily update the repository. Unfortunately this raises a few security issues. I don't want to go into the details since it was discussed many times before in this thread. So instead we choose the so called "Update" feature, which allows the package maintainer to easily notify a user about a new update. The update feature has at least two drawbacks, beside the confusion:
1. You have to install the package from the central repository first. Although technically OPM can install directly from an update page, it's not allowed because of the possible unresolved dependency issues
2. It's not 100% safe. I mean a package maintainer with bad intention, it can(at least in theory) install a malware, especially under windows
On the other hand the update feature also has a great advantage: it removes the workload from the central repository and pass it to the package maintainers, this way making the whole system sustainable in the long run.
Unifying the Install/Update button(@esvignolo suggestion) I'm not sure will solves the problem, in my opinion it will lead to even more confusion. The user will have no idea from where the package is installed(repository or update). Now at least you know(again I agree it's a little bit confusing), especially if your read the wiki page(section "Difference between download/install/update"):
http://wiki.freepascal.org/Online_Package_Manager#Difference_between_download.2Finstall.2Fupdate