Re: question on policy of renaming an extension

Please don't associate being moved to PECL with whether or not the extension is distributed as a standard PHP extension in the distribution tarball or not. The two have nothing to do with each other. -Rasmus On Sun, 20 Jun 2004, Jan Lehnardt wrote: > --[PinePGP]--------------------------------------------------[begin]-- > Hi, > On 20 Jun 2004, at 19:42, Brad House wrote: > > When PECL is better adopted by the community, and PHP provides > > documentation on them, I would have no problem moving it there. > > Following Rasmus' mail, moving your extension also increases > the convenience for you the developer and the users. > As a developer you're no longer tied to PHP's release > schedule, but you are free to release a new version whenever > you want. For the users of your extension it means, they can > have an updated version (be it a bug- or security-fix) anytime > you release it and not only when a PHP version comes out. > > Installing a PECL based extension is as easy as > $ pear install foobar > > See http://pecl.php.net/ for more information. > > Jan > -- > GPG Key: BB96 56B0 > Q: Thank Jan? - A: http://geschenke.an.dasmoped.net/ > --[PinePGP]----------------------------------------------------------- > gpg: WARNING: using insecure memory! > gpg: please see http://www.gnupg.org/faq.html for more > information > gpg: Signature made Sun 20 Jun 2004 11:05:40 AM PDT using DSA key ID BB9656B0 > gpg: Good signature from "Jan Lehnardt <jan@dahlia.dasmoped.net>" > gpg: aka "Jan Lehnardt <jan@lehnardt.de>" > gpg: aka "Jan Lehnardt <jan@php.net>" > gpg: aka "Jan Lehnardt <jan@dasmoped.net>" > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the owner. > Primary key fingerprint: 7BCC EB86 8313 DDA9 25DF 1805 ECA5 BCB7 BB96 56B0 > --[PinePGP]----------------------------------------------------[end]-- >