Рекурсивный акроним словосочетания «PHP: Hypertext Preprocessor»

Добро пожаловать на форум PHP программистов!

За последние 24 часа нас посетили 17204 программиста и 1838 роботов. Сейчас ищут 1540 программистов ...

Оглавление

About the manual Предисловие Basic concepts all PEAR users should understand Installation (Pyrus)Installation (PEAR)Command line installer (PEAR)Dependency Tracking (Meta Packages) with PEAR

Using Pyrus, the PEAR Installer for PHP 5.3+

About Pyrus Commands available in Pyrus Pyrus configuration Differences from the PEAR Installer Creating plugins for Pyrus Developer Tools for Pyrus Using Pyrus in your programs: Pyrus's Public API

PEAR Developer Guide

About PEAR and PEAR2 Becoming a PEAR developer: how to get involved PEAR Developer Guide Coding Standards PEAR Installer: Core components (Installer API, error handling)PEAR Installer: customizing the installer itself RFCs

Channels: distributing your packages

channel.xml, REST, XML-RPC Creating your own channel with Pyrus and PEAR2_SimpleChannelServer

Initial cleanup

Вернуться к: Orphan PEPr proposals

Initial cleanup

To get this process running, an initial cleanup is required. The procedure is only run once, when this proposal gets accepted. This cleanup should have the following steps:

Proposals in stages "proposal" and "draft"

PEAR QA will post a reminder comment to every proposal which shows no action since 4 weeks. If the proposer is not reachable within 1 week, the proposal is deleted.

Proposals in stage "finished"

PEAR QA will try to get in touch with the proposers of every proposal which is older than 4 weeks and for which no package has been registerd, yet. If the proposer is not reachable within 2 weeks, the proposal is marked as orphan.

Вернуться к: Orphan PEPr proposals