The ultimate composer install/update conflicts guide #11644
javaDeveloperKid
started this conversation in
General
Replies: 1 comment 3 replies
-
Part 2
|
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been installng or upgrading applications for years but sometimes I feel helpless. I understand conflicts like one package cannot be installed because it requires another package on another version. But the are many sentences I can't understand. Examples:
vendorA/package[1.16.0, ..., 1.16.2] require vendorB/package ^2 -> found vendorB/package[2.0.0, 2.1.0] but these were not loaded, likely because it conflicts with another require.
- what does it mean "likely because it conflicts with another require"? This means nothing to me. It either conflicts or not.Root composer.json requires vendorA/package ^1.9 -> satisfiable by vendorA/package[1.16.0, 1.16.1, 1.16.2]
- what's the point of this line? If we're listing Problems why to show correctly resolved dependencies?There should really be a guide to understand this awkward output.
Another difficulties I want to mention:
composer update
with the same version I already have it locked at to get rid of compaint?with-dependencies
orwith-all-dependencies
only for deps that must be upgraded and leave these that can stay at the current versions?Beta Was this translation helpful? Give feedback.
All reactions