Re: Moving extensions to PECL

From: Date: Tue, 01 Jan 2002 17:36:57 +0000
Subject: Re: Moving extensions to PECL
References: 1 2  Groups: php.dev 
Request: Send a blank email to php-dev+get-75508@lists.php.net to get a copy of this message
From: "Adam Dickmeiss" <adam@indexdata.dk> > On Mon, Dec 31, 2001 at 01:38:48PM -0500, Jon Parise wrote: > > I think the following "standard" extensions should be moved to > > PECL: > > > > ext/cybercash > > ext/icap > > ext/pfpro > > ext/yaz > > > > This is definitely not an inclusive list; it's just a start. I > > can't imagine a lot of people using these modules, so they seem > > like good candidates for removal from the base PHP distribution. > > > > Are there any well-founded objections to this (either in practice > > or principle)? > > I'll be happy to move yaz away. I hope that moved away extensions > will not be "invisible" in the future. We use yaz and a lot of our > users in the Libraries world are too. > > If this means that the documentation for YAZ which I wrote will no > longer be translated to other languages we can live with that. > > The good thing about the move is that extensions will have an > independant release-cycle so that they don't have to wait for > official PHP releases, etc. > > Note, that as extensions move away from the core, it'll be not > be obvious when there are Zend API changes unless we're informed. > (so far, people have patched yaz for Zend API changes, thank you). > > So what's the procedure? Creating pear/XML/yaz and move stuff > to that directory? Moving documentation? How? Well, I know librians will love the YAZ extension. I suggest to move the documentation in a new part in the PHP Manual. I think of a split of the original Function Reference in something like Basic Function Reference and Extended Function Reference. I don´t see any improvement if it is hidden in the PEAR docs. -Egon

« previous php.dev (#75508) next »