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 | 0000002689 2.63 KB | |
| _link | 0000000124 124 Bytes | |
| _service | 0000000469 469 Bytes | |
| php-composer.changes | 0000025934 25.3 KB | |
| php-composer.spec | 0000002234 2.18 KB |
Revision 23 (latest revision is 80)
Johannes Weberhofer (weberho)
accepted
request 596491
from
Yunhe Guo (guoyunhebrave)
(revision 23)
- Use download_url service - Version 1.6.4 * Security fixes in some edge case scenarios, recommended update for all users * Fixed regression in version guessing of path repositories * Fixed removing aliased packages from the repository, which might resolve some odd update bugs * Fixed updating of package URLs for GitLab * Fixed run-script --list failing when script handlers were defined * Fixed init command not respecting the current php version when selecting package versions * Fixed handling of uppercase package names in why/why-not commands * Fixed exclude-from-classmap symlink handling * Fixed filesystem permissions of PEAR binaries * Improved performance of subversion repos * Other minor fixes
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.