Add the ability to override package versions via the UI and add other requirements [#1931200]

As a follow up to #1931198: Add conflict detection when different modules require different versions of the same package, it would be great to have a mechanism in the UI that can resolve dependencies and override the versions set in the composer.json files.

Comments

Comment #1

cpliakas CreditAttribution: cpliakas commented 1 March 2013 at 14:39

Component:

Miscellaneous

» Code

Comment #2

cpliakas CreditAttribution: cpliakas commented 15 March 2013 at 14:21

Title:

Add conflict resolution and version overrides

» Add the ability to override package versions via the UI and add other requirements

Changing title.

Comment #3

RobLoach

he/him

CreditAttribution: RobLoach commented 19 March 2013 at 18:09

This is an interesting idea, as you'd think the module should determine which version of the package gets installed rather than the user.

In any case, happy birthday!

Comment #4

cpliakas CreditAttribution: cpliakas commented 20 March 2013 at 13:59

In any case, happy birthday!

Thanks! 31, act like 13.

as you'd think the module should determine which version of the package gets installed rather than the user.

Normally, yes. However, there are two use cases where this would be useful.

1) On hosting providers that are stuck on PHP <5.3.3 there may be instances where you have to use a package with a lower requirement. Take Git Wrapper. The library requires some Symfony components that would normally resolve to the 2.2.* version. The problem is that these components require PHP >= 5.3.3, so they potentially wouldn't work on the hosting providers mentioned above. Since Git Wrapper works with versions ~2.0, the user should be able to say "I want to 2.0.*".
2) If a module requires version "1.0.1" of a library and another module requires "1.0.2" of a library, the user should be able to say "use 1.0.1 (or 1.0.2)" without having to patch one of the modules.

Let me know if these don't make sense.
Chris

Comment #5

Grayside CreditAttribution: Grayside commented 27 May 2013 at 22:05

I thought the idea is Composer resolves that problem, and if one module happens to be compatible with the different library version, it's compatibility specification should be changed. E.g., you don't resolve this conflict locally, you submit a pull request.

Comment #6

cpliakas CreditAttribution: cpliakas commented 27 May 2013 at 23:55

I thought the idea is Composer resolves that problem

For dependency conflicts, yes, but this is when different modules have different requirements for the same package. Since Composer Manager has to merge the requirements into one, which version does it honor? This is a step before Composer has a crack at it.