Re: [PDO] Re: [PHP-DEV] Fw: [PDO] [RFC] An Idea for PDO 2

[email protected] ("Steph Fox")
Newsgroups php.internals,php.pdo
Organization Zend Technologies
Message-ID <000e01c8660b$3e3f2c20$c6fc1f3e@foxbox>
Personally I do a full pecl checkout alongside my php-src checkout, every 
time. The problems with that tend to come out during the build.

----- Original Message ----- 
From: "Marcus Boerger" <[email protected]>
To: "Steph Fox" <[email protected]>
Cc: <[email protected]>; "internals" <[email protected]>
Sent: Saturday, February 02, 2008 11:16 PM
Subject: Re: [PDO] Re: [PHP-DEV] Fw: [PDO] [RFC] An Idea for PDO 2


> Hello Steph,
>
>  you would not checkout php-default. That would only be used for release
> management. Instead you would checkout php-src and whatever pecl modules 
> you
> wanted, just as you do today. And that includes that you can choose 
> whether
> you like CLA modules or not. Just as today you do not get all PECL 
> modules.
>
> marcus
>
> Saturday, February 2, 2008, 8:52:44 PM, you wrote:
>
>>>  all we need is to extend the PECL database with a license type field 
>>> and
>>> a
>>> CLA flag. Nothing else is required at that end. But we should still move
>>> as
>>> much from php-src/ext to pecl as we can.
>
>> Hm but then when you checked out you'd have CLA'd stuff as well as normal
>> PECL stuff, as now. Don't you find you automatically tend to fix things 
>> if
>> they're broken? I know I do... even if I rarely get around to posting 
>> those
>> fixes (because once everything works here I go on to the stuff I wanted 
>> to
>> do and forget there was even a problem, until the next time.)
>
>> I was just trying to find a way that would be acceptable to php.net and 
>> also
>> would mean PDO2 driver development doesn't have to wait on PECL process
>> decisions, but actually my off-list feedback says even a PECLA module
>> wouldn't be an acceptable option for some.
>
>> - Steph
>
>>> marcus
>
>
>
>
> Best regards,
> Marcus
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.