Am 24.07.2012 22:41, schrieb Lester Caine:
Sebastian Krebs wrote:
The question is - Is the result E_STRICT safe?
Would say: Depends on the package you use. I don't use PEAR-packages
myself,
thus I don't really know. I would say: Try it out :) Test it on your
dev-machine, or within a vm and nothing can break.
Sebastian I'm asking because what I have, which I think is the latest
version of PEAR, is throwing numerous E_STRICT errors!
Didn't you say you use the builtin packages from suse? I guess they are
_not_ the latest :X
I'm trying to establish if this is actually correct, and that PEAR has
never been brought up to date, or I'm still hitting a pre E_STRICT
version.
As mentioned: That depends on the packages. There are packages, that are
completely unmaintained nowadays. However, I have some tools, that
relies on PEAR-packages and I've seen no E_STRICT for a while now, which
makes me think, that at least some, if not all, are PHP5.4-compliant.
I suspect the former which is not very helpful when I've been
told simply to fix my own E_STRICT problems ... I don't have time to
rework PEAR as well as the libraries I've already fixed :(
So is E_STRICT simply something that should be thrown in the bin and the
defaulting ON in PHP5.4 is somewhat premature?
On my dev machine I use the same settings and it works well (I use
Ubuntu, but I cannot imagine, that this makes such a huge difference).
Did you try this in the meantime? (Replace "sudo" with the "execute as
root" suse uses ;))
$ sudo pear update-channels
$ sudo pear upgrade pear
$ sudo pear update-channels
$ sudo pear updrade --alldeps
Don't know, if 'update-channels' twice is really required, but it's
doesn't hurt and I have the pear installer in mind with some curious
behaviours ;)
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
