Skip to content

Conversation

@morvans
Copy link

@morvans morvans commented Feb 6, 2017

This PR allows to force the patchLevel used to apply patches on a particular package.
Its useful for packages like drupal/core which packages only a subdir of the original upstream project on which patches are based.

    "extra": {
        ...
        "patchLevel": {
            "drupal/core": "-p2"
        }
    }

This solves #43

@cweagans
Copy link
Owner

cweagans commented Feb 6, 2017

I would prefer to not do this in 1.x. This feature is already implemented in 2.x.

@jhedstrom
Copy link

I'd advocate to get this in to 1.x since it's not a new feature but rather the only way to work around core patches being applied in the wrong place.

jhedstrom added a commit to jhedstrom/composer-patches that referenced this pull request Jan 12, 2018
kevin-dutra added a commit to kevin-dutra/composer-patches that referenced this pull request Jan 12, 2018
jhedstrom added a commit to jhedstrom/composer-patches that referenced this pull request Jan 12, 2018
adam-dg pushed a commit to adam-dg/d8-quickstart that referenced this pull request Nov 25, 2018
…er Patches struggles with patches that introduce new file. The solution is to upgrade to the 1.x-dev branch of Composer Patches and add some extra config to Composer.json

See:
- cweagans/composer-patches#199
- cweagans/composer-patches#43
- cweagans/composer-patches#101
- rwohleb/composer-patches#1
stucki pushed a commit to stucki/composer-patches that referenced this pull request Sep 14, 2021
stucki pushed a commit to stucki/composer-patches that referenced this pull request Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants