I like your idea, but I'm not the one that will do it real or takes the decision of making it real. And positions against the automated stuff are always on.
I totally agree. "The man who pays the piper calls the tune"
Let's see which sustainable system for package maintainers @GetMem settles on.
No harm in proposing ideas - @GetMem is a reasonable person; open to ideas AFAIK.
On the other hand, if I don't mantain the package anymore and the download get's broken, the repository will not have that component anymore.
With the system as proposed: the auto-checking would automatically remove the component from the master tree if the URL went bad. That's correct behavior for unmaintainable/obselete components, surely? That's why many components from the ccr were not included in the initial master list AFAIK.
So is not only merging the main json, but the zip files. This was talked some days or weeks ago in this thread, and there is no consent about how to manage this.
Why merge the zip files on the OPM server by default? The initial (vetted) zips can be canonical. The
user chooses to update their
local repository or not (with a suitable warning). The 'Available' column reflects the 'available update version'. That makes sense for a user. I thought that was the point of the 'force update' option in the update json - where the canonical version is somehow faulty or out-of date and
has to be replaced on the server - not
default behaviour.
I'm trying to look 3 - 5 years ahead with Laz 2.x/OPM when active maintenance of OPM may not be so available as now.
I'm very enthusiastic about @GetMem's initiative - it was an needed idea for Lazarus waiting to happen, and makes Lazaus look more professional to new and old users alike.