You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The patches field allows listing patches that are applied sequentially to the source as with the patch command, however not all patches are created equal. For instance, Git has a custom format for binary diffs that the venerable patch utility doesn't understand. In order to support such patches, the patch utility should be changed to git apply (although I haven't yet checked if that works outside a git repo). An example of a binary file that cannot be patched easily today is the configure script from the OCaml compiler.
The text was updated successfully, but these errors were encountered:
It is not possible ftm to specify a patch command, as for make, curl, etc. [g]patch is an opam required tool, but even if git is widely used, it is not required by opam. There is several issues where pops the idea to use an ocaml written patch, to get ride of some patch limits (see #3782 (comment)).
Early versions of the Windows patches used git apply during 2.0 development... it was unreliable which is why the patch rewriter got added. It just swaps one set of problems for another 😉
The
patches
field allows listing patches that are applied sequentially to the source as with thepatch
command, however not all patches are created equal. For instance, Git has a custom format for binary diffs that the venerablepatch
utility doesn't understand. In order to support such patches, the patch utility should be changed togit apply
(although I haven't yet checked if that works outside a git repo). An example of a binary file that cannot be patched easily today is the configure script from the OCaml compiler.The text was updated successfully, but these errors were encountered: