This is accomplished with the following
command:
%>pear upgrade pear
If your version of a package corresponds with the latest release, you??™ll see a message
that looks like the following:
Package 'PEAR-1.4.9' already installed, skipping
If for some reason you have a version that??™s greater than the version found in the
PEAR repository (e.g., you manually downloaded a package from the package author??™s
Web site before it was officially updated in PEAR), you??™ll see a message that looks like
this:
Package 'PEAR' version '1.4.9' is installed and 1.4.9 is > requested '1.4.8',
skipping
Otherwise, the upgrade should automatically proceed. When completed, you??™ll see
a message that looks like the following:
downloading PEAR-1.4.10.tgz ...
Starting to download PEAR-1.4.10.tgz (106,079 bytes)
........................done: 106,079 bytes
upgrade ok: PEAR 1.4.10
Upgrading All Packages
It stands to reason that you??™ll want to upgrade all packages residing on your server,
so why not perform this task in a single step? This is easily accomplished with the
upgrade-all command, executed like this:
%>pear upgrade-all
322 CHAPTER 11 ?– PEAR
Although unlikely, it??™s possible some future package version could be incompatible
with previous releases. That said, using this command isn??™t recommended unless
you??™re well aware of the consequences surrounding the upgrade of each package.
Pages:
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398