rfc:deprecate-pear-include-composer
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| rfc:deprecate-pear-include-composer [2016/09/04 01:50] – Add clarifications recommended by Rowan Collins davey | rfc:deprecate-pear-include-composer [2016/09/04 01:51] – davey | ||
|---|---|---|---|
| Line 29: | Line 29: | ||
| - An ecosystem of packages built to those guidelines | - An ecosystem of packages built to those guidelines | ||
| - | This proposal does not affect 2-4, and only proposes that we stop bundling (1), and instead bundle composer as a modern alternative. | + | This proposal does not affect 2-4, and only proposes that we deprecate/stop bundling (1), and instead bundle composer as a modern alternative. |
| Additionally, | Additionally, | ||
| Line 36: | Line 36: | ||
| - A default channel for the extension management tool, at pecl.php.net | - A default channel for the extension management tool, at pecl.php.net | ||
| - | Because (1) is an alias of the PEAR command-line tool, removing the latter, will also remove the former. Therefore we are proposing the inclusion of pickle instead, as a natural (backwards compatible) companion to composer. | + | Because (1) is an alias of the PEAR command-line tool, deprecating/ |
| ===== Backward Incompatible Changes ===== | ===== Backward Incompatible Changes ===== | ||
rfc/deprecate-pear-include-composer.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1