(Created page with "* 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 "ph...") |
No edit summary |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
As dicussed on IRC, I choose php-packagist which is only 1 composer repo (mostly the only one really used) for simplicity. | 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). | 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)'' | |||
=> ok. php-composer(foo) used. | |||
Notice, some packagist name to package name example (already in our repository) | |||
<pre> | |||
"fabpot/goutte": "php-goutte", | |||
"fzaninotto/faker": "php-Faker", | |||
"jms/parser-lib": "php-JMSParser", | |||
"justinrainbow/json-schema": "php-JsonSchema", | |||
"kriswallsmith/assetic": "php-Assetic", | |||
"klaussilveira/gitter": "php-gitter", | |||
"michelf/php-markdown": "php-markdown", | |||
"mikey179/vfsStream": "php-mikey179-vfsstream", | |||
"sabberworm/php-css-parser": "php-PHP-CSS-Parser", | |||
"sdboyer/gliph": "php-gliph", | |||
"seld/jsonlint": "php-jsonlint", | |||
"solarium/solarium": "php-solarium", | |||
"twig/twig": "php-twig-Twig", | |||
"zendframework/zendframework1": "php-ZendFramework", | |||
"bartlett/php-compatinfo": "php-bartlett-PHP-CompatInfo", | |||
"bartlett/php-reflect": "php-bartlett-PHP-Reflect", | |||
"sabre/dav": "php-sabre-dav", | |||
"sabre/event": "php-sabre-event", | |||
"sabre/http": "php-sabre-http", | |||
"sabre/vobject": "php-sabre-vobject", | |||
"phploc/phploc": "php-phpunit-phploc", | |||
"phpunit/dbunit": "php-phpunit-DbUnit", | |||
"phpunit/phpcov": "php-phpunit-phpcov", | |||
"phpunit/php-code-coverage": "php-phpunit-PHP-CodeCoverage", | |||
"phpunit/php-file-iterator": "php-phpunit-File-Iterator", | |||
"phpunit/php-invoker": "php-phpunit-PHP-Invoker", | |||
"phpunit/php-text-template": "php-phpunit-Text-Template", | |||
"phpunit/php-timer": "php-phpunit-PHP-Timer", | |||
"phpunit/php-token-stream": "php-phpunit-PHP-TokenStream", | |||
"phpunit/phpunit": "php-phpunit-PHPUnit", | |||
"phpunit/phpunit-mock-objects": "php-phpunit-PHPUnit-MockObject", | |||
"sebastian/comparator": "php-phpunit-comparator", | |||
"sebastian/diff": "php-phpunit-diff", | |||
"sebastian/environment": "php-phpunit-environment", | |||
"sebastian/exporter": "php-phpunit-exporter", | |||
"sebastian/finder-facade": "php-phpunit-FinderFacade", | |||
"sebastian/git": "php-phpunit-git", | |||
"sebastian/phpcpd": "php-phpunit-phpcpd", | |||
"sebastian/phpdcd": "php-phpunit-phpdcd", | |||
"sebastian/version": "php-phpunit-Version", | |||
</pre> |
Latest revision as of 12:31, 2 June 2014
- 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)
=> ok. php-composer(foo) used.
Notice, some packagist name to package name example (already in our repository)
"fabpot/goutte": "php-goutte", "fzaninotto/faker": "php-Faker", "jms/parser-lib": "php-JMSParser", "justinrainbow/json-schema": "php-JsonSchema", "kriswallsmith/assetic": "php-Assetic", "klaussilveira/gitter": "php-gitter", "michelf/php-markdown": "php-markdown", "mikey179/vfsStream": "php-mikey179-vfsstream", "sabberworm/php-css-parser": "php-PHP-CSS-Parser", "sdboyer/gliph": "php-gliph", "seld/jsonlint": "php-jsonlint", "solarium/solarium": "php-solarium", "twig/twig": "php-twig-Twig", "zendframework/zendframework1": "php-ZendFramework", "bartlett/php-compatinfo": "php-bartlett-PHP-CompatInfo", "bartlett/php-reflect": "php-bartlett-PHP-Reflect", "sabre/dav": "php-sabre-dav", "sabre/event": "php-sabre-event", "sabre/http": "php-sabre-http", "sabre/vobject": "php-sabre-vobject", "phploc/phploc": "php-phpunit-phploc", "phpunit/dbunit": "php-phpunit-DbUnit", "phpunit/phpcov": "php-phpunit-phpcov", "phpunit/php-code-coverage": "php-phpunit-PHP-CodeCoverage", "phpunit/php-file-iterator": "php-phpunit-File-Iterator", "phpunit/php-invoker": "php-phpunit-PHP-Invoker", "phpunit/php-text-template": "php-phpunit-Text-Template", "phpunit/php-timer": "php-phpunit-PHP-Timer", "phpunit/php-token-stream": "php-phpunit-PHP-TokenStream", "phpunit/phpunit": "php-phpunit-PHPUnit", "phpunit/phpunit-mock-objects": "php-phpunit-PHPUnit-MockObject", "sebastian/comparator": "php-phpunit-comparator", "sebastian/diff": "php-phpunit-diff", "sebastian/environment": "php-phpunit-environment", "sebastian/exporter": "php-phpunit-exporter", "sebastian/finder-facade": "php-phpunit-FinderFacade", "sebastian/git": "php-phpunit-git", "sebastian/phpcpd": "php-phpunit-phpcpd", "sebastian/phpdcd": "php-phpunit-phpdcd", "sebastian/version": "php-phpunit-Version",