Description: ------------ When a package is marked as deprecated the corresponding section in the manual should show this.

This is an issue that can only be solved in pearweb IMO. The manual build process doesn't know about which packages are deprecated. And adding notes to every page for every deprecated page is too much work. Easy solution: Use my package detection (it's used for providing the links to package info page, to the API docs, and to the bug tracker) and put a note on top of every manual page that is related to a deprecated package. I'll take care of it for 1.17.0.

Well the build process could query the REST service and find out that way, then we could have the manual well more static since it only happens once every week instead of on each load :P My 2 cents

better yet - how about a cron job that checks manual pages for a deprecated package and mails the pear-doc list once a month?

Greg, if PEAR would have a documentation team (like PHP has), such a reminder email would help. My proposal is also not the best because this automatic solution wouldn't be easy for subpackages and other exceptions. Helgi's proposal would have the benefit that all variants of the docs (HTML, website, CHM etc.) would be affected, but would have the same problem as my proposal. => Adding this information manually seems to be the only reasonable solution. Problem: Who will do it? To preserve the task of adding the information, we could generate a doc bug for the package that is marked deprecated. This could be done once for all currently deprecated packages, and then directly after marking a package as deprecated.

good, the last suggestion is the best

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. I did this some weeks ago.

still needs pearweb to open a bug report or send an email once a package is marked deprecated.

Were all the deprecated packages already covered or do we still need a scrip that does a one run over the database and opens up the reports ?

> Were all the deprecated packages already covered or do we > still need a scrip that does a one run over the database > and opens up the reports ? Yes, it's still needed because any package can be marked deprecated at any time.