Newsgroups: php.internals,php.pecl.dev Path: news.php.net Xref: news.php.net php.internals:36462 php.pecl.dev:5290 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74595 invoked from network); 24 Mar 2008 22:10:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Mar 2008 22:10:08 -0000 Authentication-Results: pb1.pair.com header.from=steph@zend.com; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=steph@zend.com; spf=permerror; sender-id=softfail Received-SPF: error (pb1.pair.com: domain zend.com from 64.97.136.159 cause and error) X-PHP-List-Original-Sender: steph@zend.com X-Host-Fingerprint: 64.97.136.159 smtpout0159.sc1.he.tucows.com Solaris 8 (1) Received: from [64.97.136.159] ([64.97.136.159:64476] helo=n066.sc1.he.tucows.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F0/6B-20329-DB628E74 for ; Mon, 24 Mar 2008 17:10:08 -0500 Received: from sc1-out02.emaildefenseservice.com (64.97.139.2) by n066.sc1.he.tucows.com (7.2.069.1) id 4769F91800BBF4BC; Mon, 24 Mar 2008 22:10:02 +0000 X-SpamScore: 50 X-Spamcatcher-Summary: 50,0,0,301dbc983634c82e,03b5634cdd4bfaa1,steph@zend.com,-,RULES_HIT:355:379:539:540:541:542:543:567:599:601:945:960:967:973:980:988:989:1155:1156:1260:1277:1311:1313:1314:1345:1437:1515:1516:1518:1535:1542:1587:1593:1594:1711:1712:1730:1747:1766:1792:2073:2075:2078:2110:2198:2199:2376:2393:2525:2553:2561:2565:2682:2685:2692:2828:2857:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3027:3355:3622:3865:3866:3867:3868:3869:3870:3871:3872:3873:3874:3934:3936: 3938:3941:3944:4250:4886:5007:6119:6261:7653:7679:7809:7875,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:none,DNSBL:none X-Spamcatcher-Explanation: Received: from foxbox (62-31-252-198.cable.ubr07.shef.blueyonder.co.uk [62.31.252.198]) (Authenticated sender: steph.fox) by sc1-out02.emaildefenseservice.com (Postfix) with ESMTP; Mon, 24 Mar 2008 22:10:01 +0000 (UTC) Message-ID: <029a01c88dfb$ec131380$c6fc1f3e@foxbox> Reply-To: "Steph Fox" To: "Pierre Joye" Cc: , "internals" References: <00dc01c88c90$c34c5cc0$c6fc1f3e@foxbox> <003701c88db8$915a4410$c6fc1f3e@foxbox> <017901c88dd1$39eb43a0$c6fc1f3e@foxbox> <01cf01c88dd9$b04e99e0$c6fc1f3e@foxbox> <024c01c88df2$2aadbb90$c6fc1f3e@foxbox> Date: Mon, 24 Mar 2008 22:10:49 -0000 Organization: Zend Technologies MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: [PHP-DEV] Re: [PECL-DEV] About that PECL versioning thing From: steph@zend.com ("Steph Fox") Hi Pierre, >> >> The only problem is for the snapshots, which >> version-dev should we use? My plan was to let the developers define >> which branch matches which version (like MYEXT_1_8 for 1.8-dev for >> example). It should be also possible to let the developers define >> which branch should be used for which php versions for the snapshots. >> >> >> I know where you're coming from, but IMHO it would make much more sense >> to >> use the existing PHP_*_* branches where the package code is *specific* >> to a >> PHP version. There's no good way for the snaps machine to know about >> 200+ >> different variations on MYEXT_1_8, and likewise there would also be no >> good >> way for a cvs client to grab all the packages for a given PHP branch out >> of >> CVS if everyone used differently-named branches to mean that. > > Now I'm a bit confused. What are yout talking about now? PHP snapshots > or PECL snapshots? releases builds? You can checkout pecl module branch PHP_5_2 and see all the symlinked extensions there for PHP_5_2, plus intl... > I can answer to the rest of your post once I know better what you are > referring to. I fear that you are making too strong relations between > pecl's cvs and PHP's cvs. I think you just haven't stumbled across that co possibility. It doesn't show up anywhere as an official PECL branch, but it does work. > As I can understand that one may like to have the same branches, I > don't want to have to use them. PHP branches do not fit well to pecl > development, as you noticed already almost all packages can be built > against all php versions. The goal is to have a stable branch and > maybe some expiremental branches (they are not really relevant in your > case, build a dll for each active PHP branch). I also build from CVS, Pierre. It's useful to me to be able to pull out PHP-branch-specific PECL modules from time to time. That said, I'd agree with you completely if it weren't for the differences in PHP 6. As things are, though, I'd imagine a lot of PECL developers could find a use for a PHP_6_0 branch that ships with/is built alongside PHP 6, and leave their otherwise working code in PECL CVS HEAD for the time being. Extension-specific experimental branches aren't really relevant to this discussion because we're focusing on distribution for now. - Steph > > Cheers, > -- > Pierre > http://blog.thepimp.net | http://www.libgd.org > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >