Re: Current Directory structure ?

Tomas V.V.Cox wrote:

Stig Sæther Bakken wrote:

["Tomas V.V.Cox" <cox@idecnet.com>]

Stig Sæther Bakken wrote:

[Christian Stocker <chregu@phant.ch>]

the script /pearweb/cron/make-packages.php creates .tgz files of all packages plus a xml-file (Packages.xml) with some relevant information about these packages. the WebInstaller uses already this xml file. the make-packages.php will run on pear.php.net in the (hopefully) near future.

Btw, there is a problem with the make-packages script as long as there are no CVS tags in any modules. The code you check out the next day may give you a package with the same version number but different files.

I guess this last should be done by a shell script in cron, that finally calls the make-packages. Or you are thinking in doing this directly from php like chora?

Two options: a script like make-packages.php, or generating the tarballs on the fly as long as they are CVS-hosted at cvs.php.net. But that'd only be for bootstrapping really, in the future when people do releases through the web interface, the tarball will either be uploaded as part of the release, or generated from a CVS release checkout.

I see only problems on generating the packages on the fly: loadaverage, mirrors, all-packages-download, ... A cron job and even a "do the cron now" button seems to me better.

Uhm, I'm not saying they should be generated on the fly when users try downloading them, but when a new release is published. It's not hard work at all, the CVS repository is on the same server, so checkouts are fast. The most time-consuming part of "pear package" is gzip, which is only minor unless we get packages that are several megabytes in size. There will be alternatives too. I have/had a prototype running that let you do the releases through XML-RPC, so you can use the "pear" tool for the whole thing, or maybe even your own web-based system (sourceforge projects could quite easily integrate with PEAR this way, for example). So the load average won't be a problem in a while, at least not from releases. Since the packages are generated in advance, mirroring and "download everything" won't give us problems either. - Stig