Problem/Motivation

Any time Package Manager causes a new package(not in active) that is a Drupal project to be added to the stage directory there is a chance that same Drupal project could be in the active code base but not installed via Composer.

If the stage is then applied then there may be 2 different version of that Drupal project.

Steps to reproduce

Proposed resolution

Possible ways we could detect these problems by checking the staged code base for any new packages of the type drupal-module, drupal-theme, others?

  1. #3305568: Create a validator that detects duplicate info.yml files in the stage on apply
  2. #3305564: Create a validator to stop newly installed packages from overwriting existing directories on apply

Remaining tasks

Figure out what we can check for

Comments

tedbow created an issue. See original summary.

tedbow’s picture

This will affect project browser

tedbow’s picture

To really determine this would need to be sure on the project name to Composer namespace conversion

tedbow’s picture

Issue summary: View changes
tedbow’s picture

narendrar’s picture

tedbow’s picture

Title: Package Manager should add validation to try avoid conflicts with non-Composer installed code » [meta] Package Manager should add validation to try avoid conflicts with non-Composer installed code
Category: Task » Plan
Issue summary: View changes
Related issues: +#3305568: Create a validator that detects duplicate info.yml files in the stage on apply, +#3305564: Create a validator to stop newly installed packages from overwriting existing directories on apply

Not sure if we need this issue still but I am linking the 2 issues where are handling this and making the current issue a meta

tedbow’s picture

Status: Active » Fixed

we have fixed the 2 issues we needed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

tedbow’s picture

Issue tags: +core-mvp