> This raises up a good point.  PEAR is starting to
> take shape and more and more extensions are moving
> into PEAR/PECL.  What do we do?  PECL extensions are 
> documented in the PEAR manual, not here.

> Since most of these extension moves are so recent,
> (4.3.0), we should probably continue to document them 
> until they are moved into the PEAR manual.

Sure:-)

> I think you should do PECL ones as well as it will really
> help the peardoc team and provide a good framework.  

Yes, but adding information about how to configure PHP for this
extensions does not make sense IMHO. Once they are in PECL there are
two possibilities:
1.) popular extension -> bundled with PHP and adding infos about
    configure options make sense.
2.) not so popular or whatever else -> not bundled with PHP.
    compile/configure Options are different, so it makes no sense to
    me to add/move this info to the docs.

[...]

> Moved extensions are mentioned in NEWS:
>   http://www.php.net/php4news

Thanks I got it:-)

Removed in 4.3
   ext/aspell
   ext/ccvs
   ext/cybercash
   ext/icap
   sapi/fhttpd

ICAP docs are deleted (at least excluded from the build process)
For aspell I suggest the same solution as for ICAP:
1.) exlude them from the build process
2.) make sure php.net/aspell points to php.net/pspell
3.) put a note in pspell like that in php.net/mcal

For CCVS the same as above with a pointer to MCVE

As far as i know there is no replacement for Cybercash.
I suggest to
1.) exclude the functions from the build process
2.) modify reference.xml containing a short note about the removal

About the moved extensions:

moved to PECL in 4.3
   ext/vpopmail
   ext/cybermut
  
 moved to PECL in 4.2.0
    ext/satellite
    ext/mailparse

As long as the docs not moved we should at least provide the users
some information about:
1.) the move
2.) where to get the code for the extensions

Ok, satellite docs are moved.

Regards
Friedhelm

P.S.:
Maybe we can find a general solution how to handle removed and moved
extensions. You made a suggestion later in the thread, it should be in
the TODO.


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to