Bug#355976: [php-maint] php4/php5 status

[Jan Wagner]

On Monday 06 November 2006 10:04, sean finney wrote:
> also, these involve generating new binary packages, which i think it
> would be wise to avoid at least until we get a fixed version of the
> current packages to etch.  we're able to avoid this with the PDO
> extensions because of the new configuration subsystem which allows
> for multiple extensions in the same package (and we already have
> packages with matching dependencies, i.e mysql/mysqli/pdo_mysql)

Okay ... taking php5 into NEW queue will be bad, thats true.

> > This reminds me that I should check current off-tree extensions if they
> > are up-to-date.
>
> i'm pretty sure most of the off-tree extensions will need to be
> recompiled, because the extension dir changes with 5.2 :(
>
> it's still not too late to turn back and upload a fixed 5.1.6 version
> instead, but i guess i assume that people agree with my reasoning
> about migrating to 5.2 ASAP.

As you described, since 5.1 is unsupported by upstream, it will be better to 
migrate to 5.2. The actual situation with php4 on sarge is _realy_ annoying! 
Switching to 5.2 will hopefully prevent us from this for some time.

Anyways ... trying to get a working tidy module into sid (and life with 
backport version). :-) (php5-pspell is allready there which I didn't noticed 
yet).

With kind regards, Jan.
-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------