http://framework.zend.com/issues/browse/ZF-7466
I assigned it to myself since I will be doing the patch when I get home.
Jeroen
On 04 Aug 2009, at 15:38, Ralph Schindler wrote:
> Hey Jeroen,
>
> I actually wouldnt patch the Zend library. ZF code is highly (or in
> most places) strives for modularity. This generally means methods
> are fairly short and succinct. If I were in your position, I would
> override the buggy class with your behavior.
>
> For example, if you found Zend_Foo_Bar::baz() to be buggy, I would
> extend that class with MyClient_Foo_Bar::baz() (the clients baz()
> will overrride Zends baz() but use everything else) and use it until
> the issue you have is fixed.
>
> What is your issue?
>
> -ralph
>
> Jeroen Keppens wrote:
>> Hi,
>> this is not 100% ZF related, but I'll ask it here anyway :)
>> A client uses ZF 1.7.0 in their project. They included the Zend
>> library as an svn:external. Works like a charm, but I just
>> discovered a bug in ZF and I'm writing a patch. I'll be submitting
>> it to Jira later (since the bug stands in the latest revision), but
>> I also want to apply the patch on the client's Zend library.
>> Does anyone have experience with this? How should I do it since I
>> can't "commit" the patch I make. I don't really want to patch it on
>> every developer's PC, test environment and live environment unless
>> I have to.
>> Thanks for your advise,
>> Jeroen
没有评论:
发表评论