For now the OPM only shows the version available in the main repository. Currently we try to figure it out, what would be the best approach for updates located at the developers site(see my previous post #295).
It will not work! Let's dump it. We now try to mix many ideas and create a half-baked hybrid which is not good for anyone.
A master package must be either in OPM's own repository or in an external repository.
Now we are planning a system where the master package is maybe in OPM repository but maybe not. It may be elsewhere but OPM does not know it before reading some external files. Uhhh ... no good!
One fact remains: the OPM admin work must be minimized to keep it well maintained also in far future.
My original idea, before other ideas got mixed, was having 3 types of sources for the packages:
- OPM repository.
- External repository with an external URL.
- Development version got directly from a revision control system (SVN, Git, automatic master.zip, whatever).
They all would be configured in the JSON config file of OPM.
(Number 4. could be a Delphinus style thing but it is not important now.)
Now I start to think we should concentrate in number 1. which is also GetMem's original idea.
Just updating the packages in OPM's repo should be made as easy as possible.
We need the FTP server.
We also need an admin tool which allows copying the packages and updating the configuration with few mouse clicks.