Hallo guys.

Thanks for the great work! I'm wondering how I can resolve dependency issues between lightning and other composer packages, such as drupal commerce. I'm aware that this is not an issue only affecting lightning, but rather an issue with managing multiple composer packages. However, I think a lot of people would want to install drupal commerce additionally to Lightning.

How can that be done? Thanks a lot!

Comments

anruether created an issue. See original summary.

balsama’s picture

We try to be a flexible as possible with our version constraints. See http://lightning.acquia.com/blog/dependency-version-contraints

What specific conflicts are you seeing? We can work with the commerce team to make sure we're not stepping on each others toes.

anruether’s picture

The issue I see is with ief:

$ composer require "drupal/commerce 8.2.x-dev"
./composer.json has been updated
No patches supplied.
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Can only install one of: drupal/inline_entity_form[8.1.x-dev, 8.1.0-alpha6].
- Can only install one of: drupal/inline_entity_form[8.1.x-dev, 8.1.0-alpha6].
- Can only install one of: drupal/inline_entity_form[8.1.x-dev, 8.1.0-alpha6].
- drupal/commerce 8.2.x-dev requires drupal/inline_entity_form 8.1.x-dev -> satisfiable by d rupal/inline_entity_form[8.1.x-dev].
- Installation request for drupal/commerce 8.2.x-dev -> satisfiable by drupal/commerce[8.2.x -dev].
- Installation request for drupal/inline_entity_form (locked at 8.1.0-alpha6) -> satisfiable by drupal/inline_entity_form[8.1.0-alpha6].

Installation failed, reverting ./composer.json to its original content.

I also opened an issue on the commerceguys website: https://drupalcommerce.org/questions/45415/drupal-8-distribution-and-com...

balsama’s picture

Status: Active » Closed (works as designed)

Looks like commerce requires HEAD of the commerce 8.x-1.x branch. Lightning will never allow a dev branch of anything - it's too risky. I would recommend opening an issue against commerce. If commerce needs something that's committed to IEF but not in a tagged release, they should be able to patch it in.

FWIW, the maintainer of IEF works for commerce guys, so I'm sure they can work around that HEAD requirement.