'svn' command can be used to update latest sources of individual packages there.
Good point.
I have a gap in my knowledge. Who makes a master.zip file?
Is automatically done, like this:
https://github.com/bgrabitmap/bgrabitmap/archive/master.zipSo if you have any GitHub repository the zip is already available. It contains the latest sources.
Maintained packages that have releases, the latest release version must be added to the JSON config file manually now.
I am not sure how GetMem planned to automate the process. There must be a way for the package maintainer to pass the version info without changing download URL (and file name).
This is quite important in future. The online package manager maintainer should have as little admin work as possible. Otherwise we will have an obsolete and outdated package repository in future, years from now.
[Edit] ... or maybe it is not too much maintenance to copy a new package and update the config. Don't know.
In any case it requires action from 2 people: the maintainer of a package and the maintainer of the online package manager.
That's the main problem of having a single JSON made by hand. If for example we have a website to upload the packages, then a database will do the trick, you do a query and get the list of packages in a generated JSON, that no one needs to mantain.
For easier auto-maintainance, there need to be instructions for developers to make their components 'OPM-friendly'. Some kind of standard versions.txt file that OPM can check (on user request) as well as including/updating the json file when committing/uploading newer versions. The instructions should be in the wiki (with a link from OPM)
That's true. a versions.txt pointing:
- The latest download source of release in zip (an URL)
- The latest version number
- All the other neccessary stuff
So the package manager database will be updated automatically, say one time per month? Of course there's no one testing the quaility of the packages with this way. Is always a responsability of the user what to trust.
So in fact you need only a list of URL's to get the data from (list of versions.txt only), process them and update the database, it will take time to process all, but not too much, since these are a few kb files.
So the submit new app will be something like:
Name of your package: Something
URL of updates: version.txt url containing all the data for the json (generated with the online package manager of course)