PHP PEAR Questions and Answers - testing tarball of PEAR 1.7.0RC1 (not 1.7.0) uploaded

Author

testing tarball of PEAR 1.7.0RC1 (not 1.7.0) uploaded

Greg Beaver

2007-11-30, 4:03 am

Hi all,

I'm not comfortable with the volume of serious problems we've been
having in the testing due to "minor" bugfixes in core elements like the
System class. As such, I've downgraded to RC1, and uploaded a testing
tarball.

There are two other open bugs that need fixing prior to the release as
well, which may push the release date back to Dec. 7, as I need some
serious testing of the changes to System::find() to ensure they are good.

Thanks for all of your work - you've caught what would have been a
dead-in-the-water release, and there are thousands of users who don't
know they are thanking you, but I do :)

tarball at http://pear.php.net/~greg/PEAR-1.7.0RC1.tgz

Greg

Carsten Wiedmann

2007-12-02, 7:08 pm

Greg Beaver schrieb:
>
> tarball at http://pear.php.net/~greg/PEAR-1.7.0RC1.tgz

If I upgrade from 1.6.2 with:
| pear upgrade http://pear.php.net/~greg/PEAR-1.7.0RC1.tgz

It would be nice, if the installer set:
| www_dir to $_channelConfigInfo['php_dir']\www
and
| cfg_dir to $_channelConfigInfo['php_dir']\cfg

at the moment it is set to:
| www_dir to PHP_BINDIR\www
and
| cfg_dir to PHP_BINDIR\cfg

Regards,
Carsten

Jorrit Schippers - nCode

2007-12-02, 7:08 pm

On Fri, 30 Nov 2007 01:18:45 -0600, greg@chiaraquartet.net (Greg
Beaver) wrote:

>tarball at http://pear.php.net/~greg/PEAR-1.7.0RC1.tgz

jorrit@jorrit-k7 ~/pear-core/tests $ pear version
PEAR Version: 1.7.0RC1
PHP Version: 5.2.5-pl0-gentoo
Zend Engine Version: 2.2.0
Running on: Linux jorrit-k7 2.6.19-gentoo-r5 #2 SMP Fri Mar 23
20:18:08 CET 2007 i686

TOTAL TIME: 04:28
676 PASSED TESTS
13 SKIPPED TESTS
4 FAILED TESTS:
/home/jorrit/pear-core/tests/PEAR_Registry/api1_0/test_listPackages.phpt
/home/jorrit/pear-core/tests/PEAR_Registry/api1_0/test_packageInfo.phpt
/home/jorrit/pear-core/tests/PEAR_Installer/test_install_cfgrole.phpt
/home/jorrit/pear-core/tests/PEAR_Command_Install/upgrade-all/test.phpt

listPackages: http://phpfi.com/280416
packageInfo: http://phpfi.com/280418

On http://wiki.pear.php.net/index.php/...Common_pitfalls I've
put up some things I encountered while testing and wanted to share
with others.

Is there a way to clean up the tests directory and remove the exp,
log, out, php and diff files? Could be useful. Besides that, a command
to only run the tests that were reported as a failure in the previous
run could be handy.

Jorrit

Gregory Beaver

2007-12-02, 10:03 pm

Carsten Wiedmann wrote:
> Greg Beaver schrieb:
>
> If I upgrade from 1.6.2 with:
> | pear upgrade http://pear.php.net/~greg/PEAR-1.7.0RC1.tgz
>
> It would be nice, if the installer set:
> | www_dir to $_channelConfigInfo['php_dir']\www
> and
> | cfg_dir to $_channelConfigInfo['php_dir']\cfg
>
> at the moment it is set to:
> | www_dir to PHP_BINDIR\www
> and
> | cfg_dir to PHP_BINDIR\cfg

Hi,

Although this would be easy to do, it is not advisable because these
directories are intended to be separate from the php files.
Incidentally, by default, php_dir is PHP_BINDIR\php

Greg

Gregory Beaver

2007-12-02, 10:03 pm

Jorrit Schippers - nCode wrote:
> Is there a way to clean up the tests directory and remove the exp,
> log, out, php and diff files? Could be useful. Besides that, a command
> to only run the tests that were reported as a failure in the previous
> run could be handy.

I would welcome a new command for test cleanup, and patches for the
other idea too.

Greg

Carsten Wiedmann

2007-12-03, 8:01 am

Gregory Beaver schrieb:
>
> Although this would be easy to do, it is not advisable because these
> directories are intended to be separate from the php files.

Well, I think, you don't see the problem.

My PEAR is installed at "/users/cwiedmann/pear", and that's the value of
$_channelConfigInfo['php_dir'] (the "PEAR directory").

Thus I have for example:
"/users/cwiedmann/pear/docs", "/users/cwiedmann/pear/data" and
"/users/cwiedmann/pear/tests"

I have rights (read/write) in this directory, and the webserver too (e.g.
for the webinstaller).

PHP_BINDIR is "/usr/local/bin" (default setting). In this directory, I have
only read/execute rights.

Now, after an upgrade, I have additional this settings:
www_dir = /usr/local/bin/www
cfg_dir = /usr/local/bin/cfg

What happens if I install a package, which uses these new roles? The
installer can't create this configured directories or put files in this
directories.

On Windows you have an additional problem:
"PHP_BINDIR" is allways set to "C:\php5". And that's in the most/many
installations a non existing directory. (And I have no rights to create a
subdirectory in "C:\")

All together, I think it's really better to (pre-)configure the directorys
in my example to:
www_dir = /users/cwiedmann/pear/www
cfg_dir = /users/cwiedmann/pear/cfg

which is:
www_dir = $_channelConfigInfo['php_dir']\www
cfg_dir = $_channelConfigInfo['php_dir']\cfg

Regards,
Carsten

Gregory Beaver

2007-12-03, 7:04 pm

Carsten Wiedmann wrote:
> Gregory Beaver schrieb:
>
> Well, I think, you don't see the problem.
>
> My PEAR is installed at "/users/cwiedmann/pear", and that's the value of
> $_channelConfigInfo['php_dir'] (the "PEAR directory").
>
> Thus I have for example:
> "/users/cwiedmann/pear/docs", "/users/cwiedmann/pear/data" and
> "/users/cwiedmann/pear/tests"
>
> I have rights (read/write) in this directory, and the webserver too
> (e.g. for the webinstaller).
>
> PHP_BINDIR is "/usr/local/bin" (default setting). In this directory, I
> have only read/execute rights.
>
> Now, after an upgrade, I have additional this settings:
> www_dir = /usr/local/bin/www
> cfg_dir = /usr/local/bin/cfg
>
>
> What happens if I install a package, which uses these new roles? The
> installer can't create this configured directories or put files in this
> directories.
>
> On Windows you have an additional problem:
> "PHP_BINDIR" is allways set to "C:\php5". And that's in the most/many
> installations a non existing directory. (And I have no rights to create
> a subdirectory in "C:\")
>
>
> All together, I think it's really better to (pre-)configure the
> directorys in my example to:
> www_dir = /users/cwiedmann/pear/www
> cfg_dir = /users/cwiedmann/pear/cfg
>
> which is:
> www_dir = $_channelConfigInfo['php_dir']\www
> cfg_dir = $_channelConfigInfo['php_dir']\cfg

Hi Carsten,

I do understand the problem. What is tricky is that your default
configuration (with no .pearrc or pear.conf) would install PHP files
into /usr/local/lib/php/pear/php, cfg files into
/usr/local/lib/php/pear/cfg and www files into
/usr/local/lib/php/pear/www. Now, add a config file and change php_dir
to /usr/local/lib/php/pear/php - the value it was at before. Now
suddenly your cfg files are installed into /usr/local/lib/php/pear/php/cfg.

In other words, what you're suggesting would introduce some wtf factor
that is not a good idea.

Pyrus and PEAR2 standards solves this problem from the beginning, but it
is simply not possible to change this in PEAR without breaking BC with
every existing version of PEAR.

Greg

Sponsored Links