Re: [RFC] Versioning rules for PHP/Zend/PEAR/Extensions

[Andi Gutmans <andi@zend.com>] > At 12:01 PM 9/26/2001 -0400, Joao Prado Maia wrote: > > >On Wed, 26 Sep 2001, Andi Gutmans wrote: > > > > > I think the key still lies in creating a repository for C extensions where > > > each extension can have its own release cycle. > > > > > > >That is also true, but we still need a reliable way to check for the > >version of specific extensions. Having just bumped into an inconsistency > >between GD 1.6.2 and GD 2.01 output, this would help a lot. > > > >However, the problem is already out there and to create code that is truly > >portable I couldn't rely on even this new (if it ever comes to life) > >feature. This sort of thing really complicates writing portable code. not > >just for different platforms but also for different versions of > >extensions. > > > >Just a repository wouldn't help much from the programmer's perspective > >IMHO, if the current situation continues. > > I agree completely. We need a way to check what version each extension > is. We have broken BC quite a bit in 4.0.7 so maybe we should add this > to 4.0.7 so that we can get this whole external C extension thing > going ASAP? Yes, definitely. But what do you think about the versioning scheme Jani proposed? - Stig -- Stig Sæther Bakken <ssb@alltheweb.com> Fast Search & Transfer ASA, Trondheim, Norway