There seem to be always two download locations:
- the one which I specify in the updatejson - this is the version in column "Update" - and which is updated by the local client in an interval specified in the "Options",
- the central repository which is updated from time to time by yourself or maybe by some process running on the server.
Is this correct?
Yes.
Without understanding this, the columns in the OPM window ("Repository", "Update") are confusing.
I agree it is confusing, but I think I did explained relatively well here(or at least I tried
):
http://wiki.freepascal.org/Online_Package_Manager#Difference_between_download.2Finstall.2FupdateDoes the user have to know these internals? Can't they be merged to one?
This is a good question. Initially the separation(install/update) was introduced for two reasons:
1. To offload the bulk of the work from the central repository to the package maintainer(s), this way making the whole system sustainable on the long run.
2. To prevent infection, which is especially important under windows. The user must know that now it will install something from the maintainer webpage, which in theory can contain malicious stuff
The ideal solution is to create login system for package maintainers, which would allow to modify the packages inside the main repository directly. Since the lazarus webpage was compromised in the past, Marc only agrees if somebody creates a cgi backend in pascal or php. Unfortunately I don't have the time or the energy to implement such a complex system, at least not now.
Another confusing information is in the column "Status/Data": spktoolbar in trunk has the version number 0.1.7 - this is what is installed on my system, but the column says "Up to date". I think this is wrong, it should be "Ahead of OPM" or "Development version
By up to date I meant: you cannot get a newer version with OPM, but I can change it to "Ahead of OPM", it sounds good.