Re: [pearweb] Managing releases

Martin Jansen wrote: > > In addition to this web thingie I once thought about creating > a PHP-GTK application, which also uses the RPC service to receive > the package information etc. and which is able to install the > packages (much like the web interface, but for use on your desktop). > But there's still _much_ more on my todo list before I'll > start thinking more detailed about this ;-). Umm... the idea of a xml rpc to also serve files/info from releases, could be a nice thing. With it we could build a cool desktop software distribution system like red-carpet, with package suscription, news, automatic updates, distributed updates across servers, etc. But let's return to the earth until we finish some required things :-) > >- The ability to show package dependencies in the web. > > I think this could be integrated in the package browser you > mentioned above, can't it? Not for the moment. The most important reason is because there is no "package dependencies" implemented yet. The second is, even if we'd have it, we still need to pass the package.xml file to the xml rpc (the best way for me would be extracting it directly from the package.tgz). > >Disadvantages: space > > IMO space isn't the probleme here: > > 16 GB should be enough for the first time :-). > We could make quick estimations: 75% of packages needs 50K (uncompressed) 11K (compressed) (XML_RPC) 25% of packages needs >500K (uncompressed) 70K (compressed) (PHPDoc) If we store 5 compressed releases and 1 uncompressed for each package, we get: Small packages: 50*1 + 11*5 = 105Kb Big packages: 500*1 + 70*5 = 850Kb For 100 packages we would need: 105*75 + 850*25 = 29125 = 28Mb Good, we could live much time with only 1Gb :-) Tomas V.V.Cox