Well I can do it, *if* the programmers want to support it. The best Idea is simple an archive (using a lib i did for example) -
taglist.library_1.4.lha
- which would have the simple contents -
taglist.library
taglist.library_020
taglist.library_040
taglist.readme
etc
Use the readme as you would in aminet, I can grab the website from that, the filename use *must* be observed (so people can rollback versions), and no other files would be allowed in the archives, that way people know exactly what they're getting. If a library (ie, certain mcc's) requires other ones, then they are permitted to be in the same one.
I can easily script the validation into my website (php), and do it so people can upload aka aminet, or pgp sign the archives, and have their pgp signature on file here, so it can automatically put it onto the site...
Pretty easy, just needs a client (arexx someone?) - and enough support ;-)
Oh, and it should be used for updates *only*, not for people getting the libraries in the first place, who knows what support files will be missing...
And as an extra - might be nice to keep an archive of dev files for these things - make it easier for us coders to find the includes and autodocs we need... ;-)
Robin