Dependency Management for PHP
https://getcomposer.org/
Composer is a dependency manager tracking local dependencies of your projects and libraries.
- Devel package for openSUSE:Factory
-
2
derived packages
- Links to openSUSE:Factory / php-composer
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout server:php:applications/php-composer && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| LICENSE | 0000001068 1.04 KB | |
| README.md | 0000002688 2.63 KB | |
| _link | 0000000124 124 Bytes | |
| composer.phar | 0001852323 1.77 MB | |
| php-composer.changes | 0000021864 21.4 KB | |
| php-composer.spec | 0000002513 2.45 KB |
Revision 18 (latest revision is 80)
Johannes Weberhofer (weberho)
committed
(revision 18)
- version 1.5.2
Full changelog: https://github.com/composer/composer/releases
Besides many fixes and improvements, there are the following new functions
* Added ability to call composer from within sub-directories of a project
* Added support for Bitbucket API v2
* Added support for GitLab API v4
* Added support for GitLab sub-groups
* Added COMPOSER_BINARY env var that is defined within the scope of a
Composer run automatically with the path to the phar file
* Capifony users beware: This release has output format tweaks
* Improved baseline psr-4 autoloader performance for projects with many
nested namespaces configured
* Improved memory usage of dependency solver
* Added --format json option to the outdated and show command
* Added --ignore-filters flag to archive command to bypass
the .gitignore and co
* Added support for outdated output without ansi colors
Comments 2
I plan to remove php-composer from Factory/Tumbleweed and add some code to php-composer2 to replace the old php-composer package. Are there any concerns against that decision? My plan is to do that transition at the beginning of October as long as there are no concerns.
I think it is totally fine. I have been using composer2 for quite a long time.