Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38195 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 193 invoked from network); 12 Jun 2008 22:02:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Jun 2008 22:02:10 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.235 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.235 rv-out-0506.google.com Received: from [209.85.198.235] ([209.85.198.235:43823] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4C/CD-15165-FDC91584 for ; Thu, 12 Jun 2008 18:02:09 -0400 Received: by rv-out-0506.google.com with SMTP id g37so3951391rvb.23 for ; Thu, 12 Jun 2008 15:02:04 -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=hvQ+DVajSYDoL7O+zTxLmhUxQLpw4t9+mX0NsrSOipo=; b=NRFAHDHsIsPnNox7F2ZEA4lB+l/tOO3a6MFQBuU5/4otSA1/nZGrHHGrTUgXuGR+QM J0+eCX5GKC42RPEobYfesL9gM6PFE2mnwHRjjxQXdf7bO+a5SN8fgId2nxNCqgQFHOoS lwV8TWqlkhkJkFhGjkhfcKBz9CnHp46t+6C8I= 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=MW24gUQG1H0tx26YhLcNZiCGzFbChvzzzrtGqXvi3ot6c8XTrwGrenKQMP1BrV1bH+ gIkww+uRbQT/76EwIY0EsXthWX5oEFLVyQsUyXqPPQSxX3WRmYqOcKFcj8/0wyV2058e Eur6XznKP7UsXDotwLeHQ2wXP8FdV0Qfhy5Io= Received: by 10.141.36.10 with SMTP id o10mr1386871rvj.176.1213308124660; Thu, 12 Jun 2008 15:02:04 -0700 (PDT) Received: by 10.140.178.14 with HTTP; Thu, 12 Jun 2008 15:02:04 -0700 (PDT) Message-ID: Date: Fri, 13 Jun 2008 00:02:04 +0200 To: "=?ISO-8859-1?Q?Johannes_Schl=FCter?=" Cc: internals In-Reply-To: <1213307495.21247.31.camel@goldfinger.johannes.nop> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1213307495.21247.31.camel@goldfinger.johannes.nop> Subject: Re: [PHP-DEV] extensions status, to move to pecl or to drop From: pierre.php@gmail.com ("Pierre Joye") hi, On Thu, Jun 12, 2008 at 11:51 PM, Johannes Schl=FCter wr= ote: > On Thu, 2008-06-12 at 16:31 +0200, Pierre Joye wrote: >> * Extension being deleted (not removed, a "cvs rm" will be done) >> >> mhash, no impact as we provide a compatibility layer via ext/hash >> (Thanks to Scott) > > We should keep this somewhere in Siberia like we did with other > extensions we removed. (PHP 4 XML stuff for instance) I was not clear, sorry. There is no point to keep it in siberia as the whole user API will still be available. You can see this move as a dependency removal. libmcrypt is not used anymore and the ext/mhash functions will be implemented using ext/hash, in ext/hash. >> * Extension looking for love (if noone raises the hand, they will end >> in PECL too) >> >> - ncurses >> I can help here for the windows port and pdcurses support on unix and >> windows. Hartmurt agreed for the move it to pecl for 5.3. > > hm, I thought this was already done, go for it. It will be done shortly. >> - smnp >> nice ext, any ISP out there willing to help? I can help for the windows= support > > Last time I checked it worked nicely and I know other user which have no > problems either, so I guess there's not much maintenance needed. The > only thing I see is implementing new parameter parsing API. > > So I don't see a reason to move it to PECL. But who knows which minimum snmp version should be supported (I say should not could)? What can I change on windows to support a decent snmp version (don't look at the version we used now :)? No one maintains it, the user base is relatively small (very small even). We have moved working extensions to pecl in the past because they were not maintained (and that's a very good reason). If you feel like you can help to maintain it, please do it. As I said earlier, I can give a hand to improve it and make it work smoothly on windows but I can't do it alone. >> Can be moved PECL >> - interbase >> - fpdf >> - fbsql >> - sybase and sybase_ct > > Moving fpdf shouldn't be a problem, for the others I can't really judge, > I don't know a user of these, but that's me. I'd to wait a couple of days but I think there is no issue to move them. -- Pierre http://blog.thepimp.net | http://www.libgd.org