Re: Quality control of PECL modules
| From: | Greg Beaver | Date: | Thu, 23 Feb 2006 05:09:03 +0000 |
| Subject: | Re: Quality control of PECL modules | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-3533@lists.php.net to get a copy of this message | ||
Wez Furlong wrote:
> I'm not sure that a single tag is going to work for this. The
> information we need is a mapping of PHP branch (or tag) to the
> known-good PECL extension branch/tag--the combinations are PHP and
> extension version dependent.
>
> I don't think that this information can be very conveniently expressed
> as CVS tags.
> Some kind of master file (or database) to hold this mapping seems to make sense.
This seems a bit over the top to me - perhaps pecl4win could do these steps:
1) exactly what it does now for snapshot .dll builds but label them as
snapshots
Then, in a nightly cron:
2) grab the list of packages from pecl.php.net/rest/p/packages.xml
3) grab the latest release version of each package from
pecl.php.net/rest/r/<packagename>/latest.txt and stable.txt (or some
variant of this process depending on speed)
I can easily whip up a simple php script using PEAR to do this, or a
more complex one that uses custom stuff with curl if it matters. My
only restriction is time - I won't be able to dive into this head first
until about 2 weeks from now.
4) for each package retrieve pecl.php.net/get/packagename-version.tgz if
it is newer
5) use the actual released pecl package to build a dll, for the latest
stable and the latest if they differ
The reason this approach is obviously better is that pecl packages
already have PHP dependency version info in them. Extensions that won't
work in PHP 4 specify that in package.xml. Again, no special database ,
extra scripting, or re-invented wheels are needed, all the info is right
there.
It isn't even necessary to download the .tgz, all we need to do is
determine the release version, grab the dependencies (which are also
available as serialized PHP in the REST at pecl.php.net), and cvs upd -r
RELEASE_1_2_3 for version 1.2.3.
This assumes, perhaps stupidly, that people have been tagging the cvs
repo on release...
Greg