Re: PECL versioning

From: Date: Wed, 19 Mar 2008 22:23:25 +0000
Subject: Re: PECL versioning
References: 1 2 3 4  Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-5184@lists.php.net to get a copy of this message
I did not see any announce on internal about that :) About IRC, well, that's no place to announce anything :-)
Over 40 emails on the subject, at the end of January. Blink and you'd have missed it.
There is only one safe way, the package version. The other informations (either in the various headers or the rc) are rarely updated or even used.
That's... not safe either. It's where I'd pick up info for releases, sure, but it's not safe info for pecl4win/snaps.
I made many tests and ask a couple of extensions developer, the best way could be to let them define what to use where. It can work for the snapshots, the releases or custom builds done on demand. We only need to add the necessary info in peclweb (DB, forms, cvs interface to list the branches for a given ext, etc.). The build system can work easily by creating a tree from various sources. That's what did the person I was refering to in the beggining of this mail. It is really flexible and should allow us to provide whatever we need.
We're obviously not having the same conversation. Giving up on this exchange :) - Steph

« previous php.pecl.dev (#5184) next »