Re: Current Directory structure ?
| From: | Tomas V.V.Cox | Date: | Thu, 09 Aug 2001 14:02:48 +0000 |
| Subject: | Re: Current Directory structure ? | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1341@lists.php.net to get a copy of this message | ||
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.
Tomas V.V.Cox