An increasing number of PHP software packages, libraries and whole programs
are distributed via pear packages.
Some of them, but numbers are increasing, make use of <tasks:replace> tags
which modify pear files.
Often these modified files have the relocated pear paths inside rpm buildroot
written to the replacement position and an increasing number of spec files
include sed statements to get rid of them once again.
I have not yet found a cleaner solution to this problem.
Another difficulty with 3rd party pear channels is that they require
relatively new pear installer versions for no real reasons. This breaks
building these packages on
In one instance, a package wanted a newer version of pear that present in
factory. I patched the requirement line down a few version numbers and then it
Still, some packages really use pear features that just did not ship with
older PHP as present in SLES & friends.
Pear is at the moment maintained as a sub package of php5.
Maybe it would make sense to have a separate, decoupled version of pear in
server:php:applications. This provides an upgrade option without update of the
php5 interpreter (which would break binary compatibility with everything
linked against it). pear itself is noarch.
Any suggestions are welcome.
Linux Consultant / Developer
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org