Re: [PEPr] Comment on Database::Mongo
| From: | till | Date: | Mon, 23 Mar 2009 17:50:56 +0000 |
| Subject: | Re: [PEPr] Comment on Database::Mongo | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-51654@lists.php.net to get a copy of this message | ||
On Mon, Mar 23, 2009 at 6:18 PM, Michael Gauthier <mike@silverorange.com> wrote:
> On Mon, 2009-03-23 at 09:41 -0700, Joe Stump wrote:
>> On Mar 23, 2009, at 9:37 AM, Kristina Chodorow wrote:
>>
>> > Hopefully this isn't a deal breaker!
>>
>> It is. It's PEAR's coding standards.
>>
>>
>> >> 5) Your exception needs to extend PEAR_Exception
>> >
>> > I did this, but I am a bit worried about people not having PEAR
>> > installed.
>> > Is PEAR/Exception.php installed automatically with PHP? If not, I
>> > don't
>> > think I should depend on it. People could just download the .tgz.
>>
>> Again, this is part of PEAR's coding standards. We don't really
>> support the type of installation you talk about. There's a reason
>> there's a CLI utility to do this (it's there to enforce dependencies
>> between packages, etc.).
>>
>
> As an possible solution, you could provide only security fixes to the
> existing package and move new development to the version that gets
> accepted in PEAR.
>
> Cheers,
>
> Mike
>
>
Additionally -- until a package hits 1.0.0. (= stable), API breaks are
allowed and BC doesn't have to be honoured.
Till