Hi Pierre,
<quote>
The only problem is for the snapshots, which
version-dev should we use? My plan was to let the developers define
which branch matches which version (like MYEXT_1_8 for 1.8-dev for
example). It should be also possible to let the developers define
which branch should be used for which php versions for the snapshots.
</quote>
I know where you're coming from, but IMHO it would make much more sense
to
use the existing PHP_*_* branches where the package code is *specific*
to a
PHP version. There's no good way for the snaps machine to know about
200+
different variations on MYEXT_1_8, and likewise there would also be no
good
way for a cvs client to grab all the packages for a given PHP branch out
of
CVS if everyone used differently-named branches to mean that.
Now I'm a bit confused. What are yout talking about now? PHP snapshots
or PECL snapshots? releases builds?
You can checkout pecl module branch PHP_5_2 and see all the symlinked
extensions there for PHP_5_2, plus intl...
I can answer to the rest of your post once I know better what you are
referring to. I fear that you are making too strong relations between
pecl's cvs and PHP's cvs.
I think you just haven't stumbled across that co possibility. It doesn't
show up anywhere as an official PECL branch, but it does work.
As I can understand that one may like to have the same branches, I
don't want to have to use them. PHP branches do not fit well to pecl
development, as you noticed already almost all packages can be built
against all php versions. The goal is to have a stable branch and
maybe some expiremental branches (they are not really relevant in your
case, build a dll for each active PHP branch).
I also build from CVS, Pierre. It's useful to me to be able to pull out
PHP-branch-specific PECL modules from time to time.
That said, I'd agree with you completely if it weren't for the differences
in PHP 6. As things are, though, I'd imagine a lot of PECL developers could
find a use for a PHP_6_0 branch that ships with/is built alongside PHP 6,
and leave their otherwise working code in PECL CVS HEAD for the time being.
Extension-specific experimental branches aren't really relevant to this
discussion because we're focusing on distribution for now.
- Steph
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
