Too late, not implementing all requested functionality, require some actions-in-the-middle (between commit to SVN and checking for update on WP), but:
- It seems to work
- It works for themes and plugins, placed at independent sources
Own WordPress update-server, reachable from WP-Admin side
- WordPress Self-Hosted Plugin Update API description of principles and usage
- Code of project (actively maintaned) on GitHub
In short:
* Solution for creating own Plugins/Themes update server (themes/plugins from this server can coexist in WordPress with extensions from default WP location)
* API-server and update-server may share the same host or work from different (TBT!)
* Updates distributed as zip-files from common updates-location
* Updating (adding new) distributed extension require changes in api/packages.php file in order to inform clients about published update
Two latest point means, that developer of distributed over server content can not only commit and relax, SVN-repository have to have some type of (smart) post-commit hook, which will be able
- zip HEAD of code
- deploy this zip to upload-folder
- update packages.php by correct new information