Re: [PHP-DEV] Re: phar and e_strict

2005-10-04 Thread Matthew Kavanagh
Matthew Kavanagh wrote: > Would that really be a problem, given that compressing a compressed file > and compressing an uncompressed file will usually yield similar sized > resultant files? > ...and I failed to see the previous email that says the same thing. Genius at work. ;) -- PHP Internals

Re: [PHP-DEV] Re: phar and e_strict

2005-10-04 Thread Matthew Kavanagh
Derick Rethans wrote: > On Mon, 3 Oct 2005, Greg Beaver wrote: > > >>> 1. zlib is required now with php, and by default php isn't installed >>> with zlib nor does configure catch this, so, while make install is >>> running and when pear is being installed make dies leaving a bad >>> installat

Re: [PHP-DEV] Re: [PEAR-DEV] Re: [PHP-DEV] Re: phar and e_strict

2005-10-04 Thread Derick Rethans
On Tue, 4 Oct 2005, Stefan Walk wrote: > On 10/4/05, Derick Rethans <[EMAIL PROTECTED]> wrote: > > On Mon, 3 Oct 2005, Greg Beaver wrote: > > > > > > 1. zlib is required now with php, and by default php isn't installed > > > > with zlib nor does configure catch this, so, while make install is

Re: [PHP-DEV] Re: phar and e_strict

2005-10-04 Thread Lukas Smith
Derick Rethans wrote: We are not ignoring it. However the single most useful feature from PEAR POV was dropped from PHP5: namespaces. That's lame, this has nothing to do with E_STRICT warnings or other dubious code. How is it dubious to support PHP4 and PHP5 with the same code base? There

Re: [PHP-DEV] Re: phar and e_strict

2005-10-04 Thread Derick Rethans
On Tue, 4 Oct 2005, Lukas Smith wrote: > Marcus Boerger wrote: > > > You should face reality that php 5 is a bit different than php 4. > > Many of the things changed in php 5 were made to support exactly pear > > development but pear is absolutley ignoring it. Why can't at least the > > things th

[PHP-DEV] Re: [PEAR-DEV] Re: [PHP-DEV] Re: phar and e_strict

2005-10-04 Thread Stefan Walk
On 10/4/05, Derick Rethans <[EMAIL PROTECTED]> wrote: > On Mon, 3 Oct 2005, Greg Beaver wrote: > > > > 1. zlib is required now with php, and by default php isn't installed > > > with zlib nor does configure catch this, so, while make install is > > > running and when pear is being installed m

Re: [PHP-DEV] Re: phar and e_strict

2005-10-04 Thread Lukas Smith
Marcus Boerger wrote: You should face reality that php 5 is a bit different than php 4. Many of the things changed in php 5 were made to support exactly pear development but pear is absolutley ignoring it. Why can't at least the things that shall be shipped in 5.1 fashion - especially since you'

Re: [PHP-DEV] Re: phar and e_strict

2005-10-04 Thread Derick Rethans
On Mon, 3 Oct 2005, Greg Beaver wrote: > > 1. zlib is required now with php, and by default php isn't installed > > with zlib nor does configure catch this, so, while make install is > > running and when pear is being installed make dies leaving a bad > > installation. > > I could elimina

[PHP-DEV] Re: [PEAR-DEV] Re: [PHP-DEV] Re: phar and e_strict

2005-10-01 Thread Justin Patrin
On 10/1/05, Marcus Boerger <[EMAIL PROTECTED]> wrote: > Hello Christian, > > Saturday, October 1, 2005, 6:13:51 PM, you wrote: > > > Helgi Þormar wrote: > >> So in a way I agree with Jani, specially since many distros are already > >> moving to 5.x > > > Maybe you should look at the installed bases

Re: [PHP-DEV] Re: phar and e_strict

2005-10-01 Thread Marcus Boerger
Hello Christian, Saturday, October 1, 2005, 6:13:51 PM, you wrote: > Helgi Þormar wrote: >> So in a way I agree with Jani, specially since many distros are already >> moving to 5.x > Maybe you should look at the installed bases of PHP instead of the PHP > version distributed with the latest dis

Re: [PHP-DEV] Re: phar and e_strict

2005-10-01 Thread Greg Beaver
Derick Rethans wrote: > On Sat, 1 Oct 2005, Greg Beaver wrote: > > >>It appears that E_STRICT is being triggered even though it is explicitly >>NOT asked for. All the same, I added another redundant >>error_reporting() call at the top of install-pear.php, re-built the >>.phar and committed to pe

Re: [PHP-DEV] Re: phar and e_strict

2005-10-01 Thread Derick Rethans
On Sat, 1 Oct 2005, Greg Beaver wrote: > It appears that E_STRICT is being triggered even though it is explicitly > NOT asked for. All the same, I added another redundant > error_reporting() call at the top of install-pear.php, re-built the > .phar and committed to pearweb. Hopefully this will f

Re: [PHP-DEV] Re: phar and e_strict

2005-10-01 Thread Marcus Boerger
Hello Pierre, Saturday, October 1, 2005, 5:04:01 PM, you wrote: > On Sat, 1 Oct 2005 16:48:47 +0200 > [EMAIL PROTECTED] (Marcus Boerger) wrote: >> Hello Pierre, >> >> Saturday, October 1, 2005, 4:24:02 PM, you wrote: >> >> > On Sat, 1 Oct 2005 16:17:19 +0200 (CEST) >> > [EMAIL PROTECTED] (Deri

Re: [PHP-DEV] Re: phar and e_strict

2005-10-01 Thread Jani Taskinen
On Sat, 1 Oct 2005, Pierre wrote: We have to modify it as the underlying code is not php5 _only_ but have to work for both php5 and php4. You haven't heard about branches either? :) --Jani -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.n

Re: [PHP-DEV] Re: phar and e_strict

2005-10-01 Thread Jani Taskinen
On Sat, 1 Oct 2005, Greg Beaver wrote: support entirely from the pear command. Until all the standard unix distros (gentoo/redhat/debian/etc.) start distributing PHP 5.x as the standard PHP version, this isn't an option. And as long as you keep it backwards-compatible, they won't upgrade.

Re: [PHP-DEV] Re: phar and e_strict

2005-10-01 Thread Pierre
On Sat, 1 Oct 2005 16:48:47 +0200 [EMAIL PROTECTED] (Marcus Boerger) wrote: > Hello Pierre, > > Saturday, October 1, 2005, 4:24:02 PM, you wrote: > > > On Sat, 1 Oct 2005 16:17:19 +0200 (CEST) > > [EMAIL PROTECTED] (Derick Rethans) wrote: > > > >> 1. not modify any error reporting setting >

Re: [PHP-DEV] Re: phar and e_strict

2005-10-01 Thread Marcus Boerger
Hello Pierre, Saturday, October 1, 2005, 4:24:02 PM, you wrote: > On Sat, 1 Oct 2005 16:17:19 +0200 (CEST) > [EMAIL PROTECTED] (Derick Rethans) wrote: >> 1. not modify any error reporting setting > We have to modify it as the underlying code is not php5 _only_ but have > to work for both php5