Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38246 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72137 invoked from network); 15 Jun 2008 10:12:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Jun 2008 10:12:09 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.231 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.198.231 rv-out-0506.google.com Received: from [209.85.198.231] ([209.85.198.231:53940] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E4/D9-06776-7FAE4584 for ; Sun, 15 Jun 2008 06:12:08 -0400 Received: by rv-out-0506.google.com with SMTP id g37so4694226rvb.23 for ; Sun, 15 Jun 2008 03:12:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=Em/SiTBWuN3h3S1/uyyYqLRtvomW3wmtvncf4+yV+sw=; b=IsRg8DiCut16Hbng4Wv39IvfdKpmRxsdBI8M0KQBzKycyH1URCBD5T+3PTX67J6xiV +70fin1fJ5Yuu8IujyvNFH4gVc+M5ewpdXwOdL6B6g+cr0NIgz03y7PNElW8zrtEt4Qk vRUig4pwDgJrBMXBOVfQLhzesdpPTI7c+kgWY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=IfyPOQgVpTBrMjaCi7EO9ee7BJt9rJjMkz3z+V8BO2e/XPTIf97ktlukup4rmdeVx8 4i4mxEkvNGQsiE6luD2MepYliLYEF90P5+RAcztsK1A0Ff/9CwyqjDgVtNaN8EQLtJiP ybX4s8PFwP16WWWw5ucLdTSUytJEdCYHp3x78= Received: by 10.141.15.19 with SMTP id s19mr2984582rvi.205.1213524725090; Sun, 15 Jun 2008 03:12:05 -0700 (PDT) Received: by 10.140.178.14 with HTTP; Sun, 15 Jun 2008 03:12:04 -0700 (PDT) Message-ID: Date: Sun, 15 Jun 2008 12:12:04 +0200 To: "Timm Friebe" Cc: internals In-Reply-To: <007001c8cec6$fc60ade0$14b2a8c0@kartofel> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <007001c8cec6$fc60ade0$14b2a8c0@kartofel> Subject: Re: [PHP-DEV] extensions status, to move to pecl or to drop From: pierre.php@gmail.com ("Pierre Joye") hi Timm, On Sun, Jun 15, 2008 at 11:05 AM, Timm Friebe wrote: > Hi, > >> Can be moved PECL >> - interbase >> - fpdf >> - fbsql >> - sybase and sybase_ct > > Sybase can be moved, it is unmaintained. I would've done this long ago if I > could, karma-wise. Let see what other thinks about this one, I'm waiting a couple of days more. > Sybase_ct works perfectly for us at 1&1 and despite feature requests that > exist and me not having put big efforts into it over the past years it > serves millions of requests a day without problems. The next big step would > be to add all the `if (unicode)`-stuff needed for PHP6 and/or to port it to > a PDO driver, which I frankly don't have time to do. And same for us. We don't the time or resources to support them (see below). But if we work together, it should be possible to keep them. Let me ask you the same than I ask to Lester, will you help us to keep sybase_ct in php-src? You don't need to know C or php internals but to actually provide tests and run them when we update the libraries or releases RC. What would rock is to have it supported by gcov (by us or somewhere else with a public report), would it be possible? > If an extension is moved to PECL, it is a bit more of a hassle to install > it: Windows: instead of enabling it in php.ini you need to download the dll > (not sure who builds that? Is it done automatically?) It was done automatically and without much checks and tests but users feedbacks after the releases. There is no need to say that it is not a good way to do it. Our position is that a dependency should be reliable, testable and easy to update. That means that people should be able to test if a dependency update or a change in the extension build/code did not break anything. As we can do it easy for extensions with a large tests suite or widely used, it is an impossible task for extensions like sybase or interbase. > / Un*x: Get a .tar.gz, > unpack, phpize, configure and make (last time I tried that didn't work for > me, must've been some wrong auto-whatever). If the release is done correctly, a simple pecl install sybase works. Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org