#434 PHP Guidelines change - composer/packagist registered packages
Closed: Fixed None Opened 8 years ago by remi.

PEAR is slowly dying. It was the "standard" packaging way for years, and a few libraries were provided outside any pear channel.

Composer is the new de-facto standard installer and dependency resolver, And packagist.org the common package repository (will use "registry" to avoid confusion with RPM repository).

While it probably doesn't make sense to use composer for RPM packaging (designed for "per-project" installation, not for "system-wide" shared libraries, so a bundled-libraries-factory), we need guidelines for package name and dependency management.

Especially as lot of active libraries/frameworks/tools have already drop PEAR support and switch to composer only distribution (symfony, doctrine, phpcompatinfo, phpunit...)

Here is the draft:

Diff from current approved Guidelines:

Mostly: introduce a new vitrual provides namespace php-composer(xxx)

Goal: make easier to track dependencies of pear packages (should slowly disappear)

draft approved (+1:6, 0:0, -1:0)

Login to comment on this ticket.