On 7/22/07, Pierre <[EMAIL PROTECTED]> wrote:
On 7/22/07, Gaetano Giunta <[EMAIL PROTECTED]> wrote: > What I do is: > - fetch list of extensions from pecl.php.net, getting the html page of > cvs.php.net/pecl4win/ and scanning it > - fetch the latest and greatest version of every extension from > pecl.php.net (I get the ext html page first, scan it for versions, and > download the last one available. The process might be extended to get > older/all versions, but imho it makes little sense, especially since > many packaged extensions do not compile as-is on win32 anyway. I > separate state info from release number, but for now do not really take > into account if it is beta or alpha) So you compile using the released package, right?
Correct (pecl4win uses pecl HEAD to compile and does not match the actual
stable releases. For example zip latest stable is 1.8.10, head is the dev tree 1.9.x).
That was the main reason behind my work: using released packages gives more confidence to admins of production systems
- if file config.w32 is missing from the package, I get it (via http) > from cvs > - compile all extensions downloaded and upload them to the db > - on next run, only newer packaged extensions are fetched, and the > process repeated > The code is an evolution of the existing pecl4win codebase. It has been > designed so that it can also download and compile stuff directly out of > cvs, as the existing version does. I did not look at all at the > snaps.php.net process/source. That's nice. It is exactly what I have in mind for peclweb. Is your build box available on a server? I wonder how we can integrate your work asap.
I am building using my home pc at the moment, and I do not think it has enough horsepower to withstand a publication via adsl. Plus I use VC 2005 express, so the dlls built are probably not usable by anybody. But I would be happy to collaborate... btw: I have already updated the build scripts, and will upload them to gggeek.altervista.org asap Bye Gaetano Cheers.
--Pierre
