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 | 0000002185 2.13 KB | |
_link | 0000000124 124 Bytes | |
composer.phar | 0001875179 1.79 MB | |
php-composer.changes | 0000028261 27.6 KB | |
php-composer.spec | 0000002234 2.18 KB |
Revision 27 (latest revision is 80)
Johannes Weberhofer (weberho)
accepted
request 628127
from
Yunhe Guo (guoyunhebrave)
(revision 27)
- Version 1.7.1 * Fixed issue autoloading plugins in require-dev in some conditions * Fixed handling of SSL to repo.packagist.org on very old PHP versions - Version 1.7.0 * Changed default repository URL from packagist.org to repo.packagist.org, this might affect people with strict firewall rules * Changed output from Updating to Downgrading when performing package downgrades, this might affect anything parsing output * Several minor performance improvements * Added the overridden platform config's PHP version in the diagnose command output * Added basic authentication support for mercurial repos * Added explicit i and u aliases for the install and update commands * Added support for show command to output json format with --tree * Added support for {glob,braces} support in the path repository's path argument * Added support in status command for showing diffs in vendor dir even for packages installed as dist/zip archives * Added --remove-vcs flag to create-project command to avoid prompting for keeping VCS files * Added --no-secure-http flag to create-project command to bypass https (use at your own risk) * Added pre-command-run event that lets plugins modify arguments * Added RemoteFilesystem::getRemoteContents extension point * Fixed setting scripts via config command * Fixed --no-plugins not being respected in a few commands
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.