[pearweb] Managing releases

Hi guys, I'm in the stage of building the package browser for the pear web, and would want to get some feedback about the way to manage releases. Now the system is based in a xml rpc service, which will receive a package file and will store it in the server (and logically will update the needed tables). That's the code yet written by Stig. With that we could list the different releases in the web and make them avaible to download. This is ok, but a little limited for me. I want to ask if it could be possible (besides store the tar file) to uncompress it somewhere. I see the following advantages with that: - The ability to build a package browser, that could show all the files of a packages (including php source code highlighting and documentation) directly from the web, without forcing user to download/install it. Something like Chora does. - The ability to build more automated tools. In example, the xml rpc service could read the package.xml file and do the properly updates (very nice for a "pear publish" command and also the web release upload page). - The ability to show package dependencies in the web. Disadvantages: space, security and perhaps time of development. In the server, files could be stored so: PEAR_TARBALL_DIR | +--<package name> | +--tar ball release 1 +--tar ball release 2 +--tar ball release 3 +--tar ball release 4 // 4-5 maximun of tgz's per package +--public // files from last stable release | + Source.php Comments? Tomas V.V.Cox