Yeah, that's why I was hoping to maintain a separate install, since it
would be easier to diff the patches.

Shawn: Thanks for the suggestion to extend, I only wanted to make
small changes to an existing function though, so it's harder to do it
that way. My other thought was to refactor the underlying code base to
make it easier.


On 7/5/09, Greg Beaver <> wrote:
> Waynn Lue wrote:
>> I wanted to makes some local edits to a PEAR package that I downloaded in
>> order to build some custom functionality into it.  What's the best way to
>> manage this process to ensure that I don't accidentally blow away any
>> changes if I update the package?  Should I just copy the entire package to
>> my own source repository, then use that directly instead of the PEAR
>> package?  And if I do it that way, is there an easy path to upgrade it?
> Best would be to follow Shawn's suggestion.  If you do need to make
> changes, you should contribute them back to the package, PEAR is an open
> public repository, it may be incorporated and help others in your
> situation as well (this is the point of PEAR and of open source).
> Greg

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to