- php-packagist(xxx) vs php-composer(xxx)
As dicussed on IRC, I choose php-packagist which is only 1 composer repo (mostly the only one really used) for simplicity. Using "php-composer" will imply to also define the repository, so php-composer(repo/vendor/library), ex php-composer(packagist/fabpot/goutte).
[siwinski 2014-05-20] What about in the future if non-Packagist repos are needed? -- just like for pear, non-pear.php.net channels are used. For example, Zend Framework has it's own repo (https://packages.zendframework.com/#composer) as well as packagist, but what if in the future they change to a private-only composer repo or only offer certain pkgs from their private repo? Could php-composer(vendor/library) imply a default repo "packagist" if not provided just like php-pear(Console_Color2) implies default PEAR channel instead of php-pear(channelname/Console_Color2)