The RiP Dev blog has posted an article describing how repos will be structured in Installer 4.0. The majority of us probably will not be extremely interested in this information but, if you have a repo that you would like to have in Installer 4.0, you will definately want to check it out. Below is a snippet of the article. You can get the full article HERE.
Installer 4 uses the new repository structure which is aimed at minimizing the traffic for both repo owner and the user, as well as expands the standard a little bit. It is still good old plists, but for the repo owner perspective, you don’t really have to mock with them… at all :)
Here’s how it works. Each package (a .zip file) now must contain a .plist file inside describing the package – including install/uninstall scripts, description, version, identifier, dependencies, and so on. It may also contain a png icon to be displayed as the package icon in the Installer.
When the repository owner puts the file in the repository directory tree (in the appropriate folder for the category), the repository engine does the rest – automagically extracts the plist (and the package icon) from the package archive, parses it, puts in the appropriate places and gets it ready to be served to Installer.
I have finished the repo engine code (it uses PHP) and is currently going to give it a test run for a few days internally, then we’ll put it in the public domain to re-use and abuse, along with a more detailed instructions on the package structure and plist keys (they are mostly the same).