Re: [PHP-DEV] CVS and PECL

2003-06-26 Thread Rasmus Lerdorf
On Thu, 26 Jun 2003, Wez Furlong wrote: > > B. Some extensions will have specific changes for a particular php-src > > branch > > > > For example, Wez had a PHP_4_3 branch in pecl/sqlite which was moved to > > PHP_4 and confused him. > > No, Jani was surprised by the symlink that caused the 4

Re: [PHP-DEV] CVS and PECL

2003-06-26 Thread Wez Furlong
> B. Some extensions will have specific changes for a particular php-src > branch > > For example, Wez had a PHP_4_3 branch in pecl/sqlite which was moved to > PHP_4 and confused him. No, Jani was surprised by the symlink that caused the 4.3 release pecl/sqlite to go away when he deleted ext/

[PHP-DEV] CVS and PECL

2003-06-25 Thread Rasmus Lerdorf
How to handle integrating PECL extensions in our development and release process is a somewhat tricky problem. We first have to recognize two basic characteristics of pecl extensions: A. Development/release schedule is independent of php-src schedule B. Some extensions will have specific change