Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to create a patch file #116

Open
zao opened this issue Feb 8, 2023 · 0 comments
Open

Document how to create a patch file #116

zao opened this issue Feb 8, 2023 · 0 comments

Comments

@zao
Copy link

zao commented Feb 8, 2023

While the documentation mentions what kind of format that patches need to be in there is no information on how one would create a patch to begin with. The question has come up a few times on Slack.

For example, my workflow for creating a patch is something like this, I'm sure there's a lot of variations on it among contributors and maintainers:

  • unpack the source tarball twice, once into foo-1.2.3.orig and once into foo-1.2.3
  • make the desired changes to foo-1.2.3
  • diff -ruN foo-1.2.3.orig foo-1.2.3 > foo-1.2.3_fix-some-problem.patch
  • edit the patch file and add a plain text section at the top of the file describing what it solves, where it's sourced from, credits/authors
  • add to desired easyconfig together with the computed checksum or suggest --inject-checksums
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

No branches or pull requests

1 participant