Sebastian Goebel wrote:
> For PHP5 I have to start go throught the code before I can estimate
> something. To do this, I need to install PHP here. To do this, seems
> I need to have at least new harddrive...

I'm not sure I see why:

- why not simply upgrade to PHP5 for the duration of this task?

- if you need both PHP4 and PHP5 at the same time, why not install
another instance of PHP? or if they can't co-exist on the same apache,
why not install another instance of apache?


frankly, I don't see the background for the thinking 'one system - one
application' that pops up on campware-all as well. you know, a Linux box
can run more applications at once!


Akos

Sebastian Goebel wrote:
> Because than the code could become incompatible with php4.

fair enough

> Update to PHP5 need to install some other packages from unstable
> branch (this is in fact the lowest level of exmination on debian)
> like glibc. No, don´t wanna do this on my standrd system.

I meant: grab the sources, compile them, and install them say under
/usr/local

it's not that hard... or, give me an account on your system, and I can
do it for you.

also: you've upgraded the ls-demo system to PHP5 already, haven't you?

> Wow. Must be new approach, never heard about this

see, these systems are very advanced you can even install multiple
versions of the same tool, at the same time!


Akos

Tomas Hlava wrote:
> There is important to use proper version of php cli intepreter.
> It's not so easy as to have the 2nd mod_php in the 2nd apache, I think.

why not?

you just put them into an alternate directory (/opt or /usr/local or
/whatever), and point the appropriate config files and environment
variables there (PATH, LD_LIBRARY_PATH, that's about it). then all's
going to be fine.

seriously, this is an easy process. note that the location you're used
to for these packages is arbitrary as well.


> I'm not very deep in the PHP5 migration, but there seems to be more
> important problem:
> Although I'm not sure yet PEAR DB package seems to be incompatible with
> PHP5 - due to newly introduced static methods. Methods not marked as
> static can't be call statically in PHP5 and in older packages no methods
> are marked static, but static calls are very often.

of course, we have to go through all our dependencies as well

>
> Now I'm looking for some "compatibility flag" in PHP5 to suppress this
> behaviour.
>
> Does anybody know something about this problem?

I don't


but, php5 compatibility is a real issue, it prevents LS from being
installed on any RedHat or Gentoo system


Akos

> > Update to PHP5 need to install some other packages from unstable
> > branch (this is in fact the lowest level of exmination on debian)
> > like glibc. No, don´t wanna do this on my standrd system.
>
> I meant: grab the sources, compile them, and install them say under
> /usr/local
>
> it's not that hard... or, give me an account on your system, and I can
> do it for you.

Sure, I would not revoke this offer! Ping me on messenger if you have time for.



> also: you've upgraded the ls-demo system to PHP5 already, haven't you?

I did. Thatswhy we were not able to use it to maintaine packages. AFIK libc6 is somehow backbone for compiling, and osteoporosis could cause many side-effects.

Doug was going to re-install, but seems not taken.


> > Wow. Must be new approach, never heard about this
>
> see, these systems are very advanced you can even install multiple
> versions of the same tool, at the same time!
>

Must be very very expensive thing! Don´t let Bill hear about, he will come out of his dll-hell and try to catch you. >

> Now I'm looking for some "compatibility flag" in PHP5 to suppress this
> behaviour.
>
> Does anybody know something about this problem?
>
> --
> Tomas Hlava
> th@red2head.com


AFIK there is no mode for full compatibility. The is only in know is ini
setting E_STRICT therewith you can increase picky behavior, but this is
disabled by default.


Sebastian