#5320 Import Python Patch

[uilianries]

The easiest way to fix our problem related to patching is by the
upstream. However, neither the upstream and their forks are maintaining
the project since 3 years ago.

So idea here is importing the original implementation and merging with the current PR in upstream.

This current PR is able to fix add/rem files using patch apply

Changelog: Fix: Add and remove out-of-tree git patches (#5320)
Docs: Omit

• Refer to the issue that supports this Pull Request.
• If the issue has missing info, explain the purpose/use case/pain/need that covers this Pull Request.
• I've read the Contributing guide.
• I've followed the PEP8 style guides for Python code.
• I've opened another PR in the Conan docs repo to the develop branch, documenting this one.

^{Note: By default this PR will skip the slower tests and will use a limited set of python versions. Check here how to increase the testing level by writing some tags in the current PR body text.}

[SSE4]

another option: https://github.com/libgit2/pygit2

[memsharded]

What am I missing here? I cannot find such patch-ng.

[uilianries]

We need to publish first our fork: https://github.com/conan-io/python-patch-ng

[lasote]

I assign to myself to review the fork and publish to pypi

[lasote]

I've published the patch-ng. Looks like it broke some test. Check please

[lasote]

We need a test for #5320. I'm not opposed to have it here in Conan.

[lasote]

These asserts here are useless... right? I want to assert the final files in the cache. So do this asserts in the build() method or access to the recipe folder in the cache.

[uilianries]

well, they are the result of patch method. I can internalize in build() but I think it will result on same thing. The original file only contains a part of the phrase, after applying the patch the phrase is complete, so the patch need to work.

[lasote]

ah, ok. I missed that is a local build() method.