Closed (fixed)
Project:
Composer Manager
Version:
8.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
16 Oct 2015 at 22:33 UTC
Updated:
30 Oct 2015 at 22:44 UTC
Jump to comment: Most recent
Let's say composer_manager was used to install the Address module.
Then, Commerce is added to the mix, and it brings a drupal/address requirement.
Composer won't know that the address module is already there, but will redownload it instead.
Discussing this at DrupalCon we concluded this is probably not the desired behavior.
Instead, we should add drupal/address to the "replace" list, so that the already present version is used instead.
Comments
Comment #2
bojanz commentedThere's a question of which version to use in the replace list. We can at least use "8.*", meaning "the package we already have at least starts with a 8.".
We can be more precise if the package declares a branch-alias (indicating which branch it is).
For example:
We should advise package authors to add this. It's a Composer best practise as well.
Comment #3
bojanz commentedCommitted.