[binarycloud-dev] ext/pear question

[Jason H. <jc...@ey...>]

alex,
i'm seeing that you've added the entire PEAR tree under ext/.  my
impression of this BC/PEAR convergence was that you were just going to
add the PEAR libraries that BC used, not the entire PEAR tree.  it just
seems sticky doing it this way because of version conflicts, and the
hassles of keeping the entire tree up to date; not to mention simple
scattered file duplication.

it would seem to me that this would be best handled one of two ways.  if
the stock PEAR modules (stock being the keyword) are to be used by BC, a
simple importing of that PEAR library would suffice.  if the needed PEAR
module needed additional tweaking to comply better with BC needs, then
it would be added to ext/pear; but only if it was a "hacked" version for
BC use.

hope this made some sense --
jason